Re:Rust’s async isn’t colored
by stefan_ on Thursday March 11, 2021 @07:07AM
(#26423152)
That is such absurd hyperbole. Just because I can wrap an async function call in 10 lines of runtime-specific boilerplate doesn't make the function color problem any less annoying.
[ Parent
| on HN ]
It stops unnecessary pollution when dealing with code you cannot control.
Often you couldn't care less about the asynchronicity of some calls.
Sometimes it's not even obvious why some things are async at all.
You're forced to make your code async even when it was never meant to be async as per your mental model.
Re:Rust’s async isn’t colored
by MaulingMonkey on Thursday March 11, 2021 @07:28AM
(#26423302)
10 lines is fairly annoying. Fortunately, the color change bit alone is just 1 line - and you can mix runtimes, although the wisdom of doing so is questionable.
println!("{}", futures::executor::block_on(library::read()).unwrap());