Rust vs Go

this is horse shit.
D is worthless without GC which makes it not qualified as a C replacement, and GC implementation is shit, so it might be not even better than Java performance-wise.

Except almost all libraries depend on GC

basically, at least read about "try" macro before shitposting

these codes are not even close to being equivalent, and the first one — I'm not sure if it is even correct

well done user

also, Go can't go without GC, so it has nothing to say in the areas where this matters (hard-realtime tasks for example)

you don't need to turn GC off if you're Google scale. Nice try, smallfry, but you'll always be small with that attitude.

At least it's not run by commie trannies.

I already have. The Rust Handbook, to be more specific, unlike you.

wiki.c2.com/?ImplicitTyping

Faggot.

read a book then hang yourself, moron

go:
if err != nil { return err}

rust:
this_might_fail()?