undefined | Better HN

0 pointskirbyfan64sos3y ago0 comments

If your program is mostly synchronous, you can manually create the async runtime and just use block_on to call async functions from a sync context: https://tokio.rs/tokio/topics/bridging#a-synchronous-interfa...

0 comments

abiro3y ago

Even simpler to use `futures::executor::block_on`. No need to create a runtime, you can just call the function.

https://docs.rs/futures/latest/futures/executor/fn.block_on....

Matthias2473y ago

That will only allow to run futures which have no IO dependency. Other typically expect a certain runtime to be running, because they eg use the epoll loop of that runtime to make progress.

mamcx3y ago

No, this not work well.

The highly infectious nature of async means you need to do that A LOT.

ie: reverse ALL things await.

That is too much. I refactor all my codebase (a huge refactor!) because this.

jen203y ago

What would you prefer the alternative to be? Library authors to do dual implementations of everything?

slightknack3y ago

A language with a function-color-agnostic effect system, generic over asynchronicity?

1 more reply

j / k navigate · click thread line to collapse