Skip to content
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

Semaphores are hard to use #85

Open
cstanfill opened this issue Jan 20, 2019 · 0 comments
Open

Semaphores are hard to use #85

cstanfill opened this issue Jan 20, 2019 · 0 comments

Comments

@cstanfill
Copy link
Collaborator

Semaphores are a little tricky to use, since independent parts of the program can watch different semaphores. If some piece of code that only cares about semaphore A gets woken up for semaphore B, it has no idea what to do about this - and can't just eat the wakeup.
Right now this can be worked around by unwatching the unexpected semaphore, and then once it's done with its semaphore logic, rewatching it and setting it for the next wait operation to pick up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant