Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think the OP meant that those who did not want async would use block_on, while the async API would just work for those who wanted to use it.


I tried to edit for clarity. The issue is the "bringing in the runtime", or the `async_std` part as you point out elsewhere. I guess I don't see a huge benefit in making a keyword like `block` that aliases `async_std::task::block_on`. Indeed you could just `use async_std::task::block_on as bock;` and be on your way.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: