In the rust example error handling is enforced via the type system whereas with Go it depends on your (and others) discipline.
Re:Why Tech Startups Should Look at Go
by shanemhansen on Thursday January 15, 2015 @06:21PM
(#8896126)
You're correct. Go doesn't leave it entirely to discipline, since unused (or unhandled) variables are a compiler error. You can silence that error with _, but it sticks out to the eye as broken code.
However I'm not trying to argue that go gives you the same type safety guarantees that rust does, it doesn't.
Thanks, I forgot about the warnings. It's been a while since I've used Go.
Its not a warning, its a "will not compile" :)
Re:Why Tech Startups Should Look at Go
by dllthomas on Saturday January 17, 2015 @02:48PM
(#8905308)
Isn't the technical term "error"?
I suppose the technical term would be "fatal error". I was just clarifying it was a warning since C compilers, for example, will happily spit out many warnings and then hand you binary-
I find that creating go backend services is super easy and simple. The builtin web server is amazingly performant. I've found it super easy to integrate with other services (cassandra, postgres, mysql, mongo, nsq). The result is always high performance apps with a low memory footprint and high test coverage.
When it comes to type systems, I find go's handling of errors to be closer to rust than c. Basically multiple return values encapsulate the same information Rusts's Result<T, E> does. You just deal with:
rather than: Rust certainly has the advantage in type safety, but I find the 2 forms mostly equivalent for the things I care about.