News for hackers. Stuff that matters.

A comment on Migrating from Go to Rust. Parent comment

Re:Migrating from Go to Rust by ventana on Monday May 25, 2026 @12:01AM (#48263288)
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.
[ Parent | on HN ]
Re:Migrating from Go to Rust by awesome_dude on Monday May 25, 2026 @01:49AM (#48263795)
Yeah - I assumed so - which makes the GP post... bizarre
[ Parent | on HN ]
Re:Migrating from Go to Rust by LtWorf on Monday May 25, 2026 @04:26AM (#48264644)
Same as in go, a language designed several decades later.
[ Parent | on HN ]
Re:Migrating from Go to Rust by ventana on Monday May 25, 2026 @12:24PM (#48268664)
Which is probably not really surprising, if we consider who were the original designers of Golang!
[ Parent | on HN ]
Re:Migrating from Go to Rust by awesome_dude on Monday May 25, 2026 @04:08PM (#48271085)
Funny - you said Go was worse - now you're saying Go's the same...
[ Parent | on HN ]
Re:Migrating from Go to Rust by LtWorf on Monday May 25, 2026 @04:19PM (#48271221)
It is worse, gcc has the warnings at least, go does not. You need a 3rd party linter.
[ Parent | on HN ]
Re:Migrating from Go to Rust by awesome_dude on Monday May 25, 2026 @04:33PM (#48271362)
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.

[ Parent | on HN ]