async/await: Sending Waker seems to invalidate it #57036
I recently started playing around with the new async/await features and wanted to implement a simple channel using the crossbeam channel and the new futures. The crossbeam channel itself isn't futures-aware, neither 0.1 futures nor the new ones, and therefore, I added another internal channel that sends wakers to the sender and when a new value is sent, the sender will wake all enqueued tasks.
My code is found in this repo: https://github.com/Janonard/rust-noopwake-bug
I expect the program to print
Is this a bug within rust, tokio or crossbeam or have I simply made something wrong?
The text was updated successfully, but these errors were encountered: