Tokio 1.0 – async runtime for Rust

Re:Tokio 1.0 – async runtime for Rust by haberman on Wednesday December 23, 2020 @05:02PM (#25522781)

I'm skimming your link trying to understand the design. It sounds like there is a global flag for whether the whole program is in evented or blocking mode?

> during compile-time, it’s possible to inspect if the overall program is in evented mode or not, and properly designed code might decide to move to a threaded model when in blocking mode, for example.

[ Parent | on HN ]

Re:Tokio 1.0 – async runtime for Rust by sanxiyn on Wednesday December 23, 2020 @05:16PM (#25522905)

Yes, it's a top level application decision, not a library decision. In fact, this is exactly how allocation and unwinding is handled in Rust.

[ Parent | on HN ]

Re:Tokio 1.0 – async runtime for Rust by zozbot234 on Thursday December 24, 2020 @10:09AM (#25528079)

So, it's like the choice of a Tokio executor? That's a top-level default, too.

[ Parent | on HN ]