“for most programmers, being able to ignore potential error states is the essential feature that they really desire from their languages.”
if the error comes from state that isn't known at compile time (FS), this seems impossible.
-
-
don't transition to or persist invalid states and most of the problems disappear.
-
you say this is an alternative to Result in Rust, but this is what Result is for in Rust.
-
I'm not saying anything about Rust, personally.
-
you literally said "the alternative I prefer" in response to a comment about Rust.
-
the original comment I was quoted for has nothing to do with it though.
-
so you're cool with using unwrap() when prototyping?
-
I personally find that defining the state space is a big part of prototyping; types are how I define the problem.
-
usually I leave out parts of the space from my types to narrow the scope of the problem instead.
- 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.