Tokio 1.0 – async runtime for Rust

Re:Tokio 1.0 – async runtime for Rust by sanxiyn on Wednesday December 23, 2020 @06:30PM (#25523510)

Yes. There are some difficult technical issues. In practice, borrow checker works less well on async code than threaded code.

This is partly why I prefer threading over async in Rust. Look, we went through some enormous effort to make threading good and fun again. Why wouldn't you use threading?

[ Parent | on HN ]

Re:Tokio 1.0 – async runtime for Rust by jen20 on Wednesday December 23, 2020 @06:50PM (#25523658)

> Why wouldn't you use threading?

Because the C10^nK problem where n increases periodically is still a thing?

[ Parent | on HN ]

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

I am not solving C10K problem.

[ Parent | on HN ]

Re:Tokio 1.0 – async runtime for Rust by btrask on Wednesday December 23, 2020 @06:54PM (#25523684)

Green threads.

[ Parent | on HN ]

Re:Tokio 1.0 – async runtime for Rust by coolreader18 on Wednesday December 23, 2020 @07:22PM (#25523883)

Those are async tasks

Or rather -- async tasks are as close as you can get to green threads in rust without a runtime that would impose overhead on every program

[ Parent | on HN ]

Re:Tokio 1.0 – async runtime for Rust by darthrupert on Thursday December 24, 2020 @12:39AM (#25525312)

Because you cannot win artificial benchmarks with threading.

[ Parent | on HN ]