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

Calling unlock twice will add cause available resources to increase outside its bounds #48

Open
mikebaldry opened this issue Sep 15, 2016 · 0 comments

Comments

@mikebaldry
Copy link

It should do some kind of sense check to now allow available resources to be greater than that defined inside your semaphore, raising an error. Otherwise you can end up with nothing at all locking.

Silly example, but an easy mistake!

s.lock(60) do
  s.unlock
end
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

Successfully merging a pull request may close this issue.

1 participant