Just a pondering.on result<(),T>

It has started from catch blocks in RFC 243, which then evolved to try blocks (see RFC 2388). After that there was @withoutboats’s pre-RFC and in the discussion several evolved variants were proposed, one of which I’ve presented in the previous message. try fn is a logical evolution considering async fn, desire for try { .. } blocks and commonness of error handling, which ideally should be more ergonomic to read and write.