1/ My biggest issue with "force you to think" is that it's touted as a self-evident good even when applied to minor issues.
@cairnrefinery I like solutions like Rust's error-handling, especially with .unwrap(), try!, and the proposed suffix-?
-
-
@cairnrefinery this keeps the error clearly, but doesn't "force you to think" about it if you don't want.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wycats I know you do, which is why your tweets surprised me! Doesn’t that fall under the ‘having to think about errors’ banner? -
@cairnrefinery not really, since "ignoring" the errors via unwrapping in Rust is the equivalent of 5 lines of Go boilerplate. -
@cairnrefinery iow, it's trivial in Rust to ignore the errors at first, and still get reasonable exiting behavior etc. -
@cairnrefinery "forcing you to think" in this case would be forcing you to use: match err { Ok(...) => ..., Err(...) => ... } -
@cairnrefinery people who believe in the "forces you to think" philosophy would thin that was a plausible answer worth considering. I do not -
@wycats Maybe a better term for that is not “forcing you to think” but “forcing you to, at the very least, at least consider” -
@cairnrefinery I use "nudge" to describe this. -
@wycats Nudging you to think? That works! - 1 more reply
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.