-
Notifications
You must be signed in to change notification settings - Fork 22
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
Non-throwing channel::read and channel::write #76
Comments
There are a few solutions
|
|
What's bad about (2) ? The value gets ignored anyhow, so a |
(1) would not work for non-default ctor-able T, so I think I should add (2) for interrupt await & (3) for channel's only. I don't think stuff like |
I'd go for |
Is this really a general issue or rather one concerning using channels in a |
In my case it was just with channels + select. I don't know enough about the library to say if this could happen under more situations. |
Would it be possible to have functions that don't throw, but return an error code, on cancellation?
The text was updated successfully, but these errors were encountered: