-
Notifications
You must be signed in to change notification settings - Fork 8
Remove runtime dependency on async-std
by implementing a custom CondVar
using the event_listener
crate.
#4
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
Conversation
move most of the `unsafe`ty into a mostly safe `AtomicBool` type
I'm reasonably certain that this is safe now. |
I'm pretty sure this is done. |
Thanks for opening this PR! - This feature has been merged as part of #10. Thanks! |
This PR completely removes the runtime dependency on
async-std
as suggested in #3.My initial approach was to use an
async-channels
channel but in this case a singleCondVar
should be sufficient.The
CondVar
implementation has only been tested by running the smoke test several times and should be reviewed.The Atomic accesses can probably all be
Relaxed
.This PR does the following:
async-std
and add it as a dev-dependencyevent_listener
CondVar
that is used in place of theasync-std
channels--features unstable
flag oncargo test
in CIunstable
feature)