News for hackers. Stuff that matters.
Re:Announcing Rust 1.13 by pcwalton on Thursday November 10, 2016 @04:00PM (#12924299)
Why? Can you explicitly name a type of mistake that might happen and explain how Go solves it in a way that Rust does not?
Re:Announcing Rust 1.13 by namelezz on Thursday November 10, 2016 @05:02PM (#12924876)
It's not really a mistake. Just coding preference. For example: do_A()?.do_B()?.do_C()?. With the one line statement like that, when weird things show up, I don't really know if it's caused by bugs in do_A, do_B, or do_C. The linear layout of Go code lets me go through each do_X call line by line and setting break points is also easier. The problem here is when I need to investigate the chain do_A()?.do_B()?.do_C()?., I may have to rewrite that statement.
Re:Announcing Rust 1.13 by pcwalton on Thursday November 10, 2016 @05:16PM (#12925013)
I agree that we should have good debugging tools for this (in particular, break on error return). But note that you can break on function calls and use "finish" to effectively go call by call to see where the error is today.
Re:Announcing Rust 1.13 by namelezz on Thursday November 10, 2016 @06:34PM (#12925726)
> use "finish" to effectively go call by call

Great tip. Thank you for the hint.