News for hackers. Stuff that matters.

A comment on Portable and Interoperable Async Rust. Parent comment

Re:Portable and Interoperable Async Rust by swiftcoder on Wednesday December 08, 2021 @03:04AM (#29482285)
It's extremely challenging to make async that is usable without introducing a garbage collector or a whole lot of runtime overhead.

A better comparison would be between the Rust and C++ paths to async - C++ also spent years designing their async system, and the end result is divisive at best.

[ Parent | on HN ]
Re:Portable and Interoperable Async Rust by dxuh on Wednesday December 08, 2021 @04:40AM (#29482770)
And we are not even done yet. The Networking TS seems to have fallen out of favor and now it seems we are going to get executors + senders/receivers, which I personally think is pretty cool actually.
[ Parent | on HN ]
Re:Portable and Interoperable Async Rust by jabl on Wednesday December 08, 2021 @06:48AM (#29483648)
Wonder if the Rust team is aware of the work on the C++ side of the fence on the executors+senders/receivers approach: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p230...

Not saying that is the ultimate answer to building async and/or parallel algorithms, but being aware of what others in the same space are doing is certainly useful.

[ Parent | on HN ]
Re:Portable and Interoperable Async Rust by pjmlp on Wednesday December 08, 2021 @05:58AM (#29483311)
True, and as the sibling comment notes it is still not fully there, yet as the vocabulary types are part of the standard library, it means what I have coded running on top of C++/WinRT, might equally work on top of HPX or cppcoro, just by changing includes and library being linked.
[ Parent | on HN ]