[kirbyfan64sos]

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...

[abiro]

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....

[Matthias247]

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.

[mamcx]

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.

[jen20]

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

[slightknack]

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

[Georgelemental]

https://news.ycombinator.com/item?id=31620340