[ventana]

C, as a language, cannot bother less about you using or not using the return values, checking them, discarding them, or using them to index an array without any bounds checking. Various linters and compilers may have their opinions, expressed as warnings, but at the end of the day it's completely up to you as a developer.

[LtWorf]

Same as in go, a language designed several decades later.

[ventana]

Which is probably not really surprising, if we consider who were the original designers of Golang!

[awesome_dude]

Funny - you said Go was worse - now you're saying Go's the same...

[LtWorf]

It is worse, gcc has the warnings at least, go does not. You need a 3rd party linter.

[awesome_dude]

One compiler (gcc) - and it doesn't do it by default

Go has go vet - baked in and runs by default

I tire of your bad faith ignorance.

[awesome_dude]

Yeah - I assumed so - which makes the GP post... bizarre