Golang's error model is so flawed. Error code propagation is error-prone and horrible for tracing where errors happen.
-
-
@wycats handling errors all the time is really redundant and its rare you care about them or hit them (so its easy to make mistakes)Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wycats and when they do happen you lose the whole call chain that produced the error code, so you don't know where it really came from -
@iamdvander I'm working on Rust's error story, which has easy propagation via try! and "unused error" lint which yells at you if you ignore -
@wycats cool! Are there any examples to look at? - End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.