-
Notifications
You must be signed in to change notification settings - Fork 78
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
Counter and channel implementations #60
Conversation
2c669a4
to
ac40e34
Compare
No need to keep old code around as the use case can be handled with Channel.
This is to keep the usage of different signals clean in the user facing API.
Hi! Great project. Are there any updates on this? |
If I recall correctly this branch worked okay last time I checked but I lack the courage to publish this as a new version because this is a widely used crate by now and I'm afraid I'm doing something stupid unless I get some code reviews for this. The code reviews may never happen, and it might be that I'll never release this branch. We will see. |
Don't hesitate to ask if there's anything I can do. |
Code reviews for this are highly appreciated to get this moving forward. |
i just tested macOS. all the examples work fine, and all tests pass |
Close to four years with no proper code reviews, I'm closing this PR. I don't expect this to be ever merged in. There are good alternatives available if you need some fancier signal handling mechanisms. |
These still need documentation and reducing the size of
unsafe
blocks. However, the functionality is there and I haven't found any bugs. I've tested the implementation on Linux, Windows, and FreeBSD.