-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Integration with loom or shuttle? #23
Comments
I would accept a PR to support loom in a similar way as crossbeam-rs/crossbeam#487. |
I looked into this a bit tonight. It seems like event-listener relies heavily on Without park, it seems like the loom version and the normal version of event-listener would have to be very different (replace park/unpark with an extra loom::sync::mutex and loom::sync::condvar?), which is not desirable. |
It seems tokio-rs/loom#133 has been resolved. |
Hi,
This package has been a lifesaver. I really unable to implement https://github.com/rmcgibbo/async-priority-channel (which whos API is basically copied completely from smol-rs/async-channel) without out.
One question: would it be straightforward/possible for event-listener to provide a hook to use loom or shuttle. I'd like to be able to test my code which depends on event-listener using these techniques if possible. tokio-rs/loom#220 seems to indicate that the latest release of loom now handles SeqCst which is probably necessary.
The text was updated successfully, but these errors were encountered: