A Look at Rust from 2012

Re:A Look at Rust from 2012 by vablings on Wednesday December 03, 2025 @10:01AM (#46135271)

I feel async is in a very good place now (apart from async trait :[ ) As a regular user who isn't developing libraries async is super simple to use. Your function is async = it must be .await and must be in an async runtime. Probably as simple and straightforward as possible. There are no super annoying anti-patterns to deal with.

The ecosystem being tokio centric is a little strange though

[ Parent | on HN ]

Re:A Look at Rust from 2012 by leshow on Wednesday December 03, 2025 @12:05PM (#46136984)

I love Rust and async Rust, but it's not true that there aren't annoying things to deal with. Anyone who's written async Rust enough has run into cancel-safety issues, the lack of async Drop and the interaction of async and traits. It's still very good, but there are some issues that don't feel very rust-y.

[ Parent | on HN ]

Re:A Look at Rust from 2012 by pornel on Wednesday December 03, 2025 @01:11PM (#46137872)

I've been writing async Rust for as long as it existed, and never ran into any cancel-safety issue. However, I also never used tokio's select macro.

[ Parent | on HN ]

Re:A Look at Rust from 2012 by junon on Wednesday December 03, 2025 @05:13PM (#46140951)

I don't really appreciate the superlative here as I too have not run into cancel safety issues in practice.

[ Parent | on HN ]