Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Understanding Rust futures by going way too deep. Parent comment
No, it's verbose and ugly. Easy to read would be something like:
fn try_join(a:A:Future<E||AR>,b:B:Future<E||BR>) -> impl Future<E||(AR,BR)>
There are no comments on this comment yet.
No, it's verbose and ugly. Easy to read would be something like:
(Rounding to the nearest Rust-like syntax where appropriate and borrowing `type (||) = Either` from Haskell.)