On 10/17/13 11:54 AM, Florian Weimer wrote:
* Chris Morgan:
I would love this to be the case. It's the biggest problem I had with Go's
error handling: that it's far too easy to just ignore a return value
accidentally.
I did an informal study some time ago, and it does not appear to be
that common a mistake. (I was biased and tried to prove that the
current state of affairs what bad, but the results weren't
convincing.) It only happens when there are no results whatsoever.
If there are results that need processing, programmers do some form of
error handling or threading.
On the other hand, Cindy Rubio-González's work shows that in the Linux
kernel, forgetting to handle error codes is *extremely* common.
http://www.eecs.berkeley.edu/~rubio/
I don't see anything fundamentally different with Go's approach that
will lead to a different outcome.
Patrick
_______________________________________________
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
