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

Ruby 2.3 compatability #127

Closed

Conversation

mariovisic
Copy link

Ruby 2.3 depreciates Thread.exclusive in favour of using Mutex
objects. Mutex has been around since ruby 1.9 so we can use it for all
versions.

Ruby 2.3 depreciates `Thread.exclusive` in favour of using `Mutex`
objects. `Mutex` has been around since ruby 1.9 so we can use it for all
versions.
@tarcieri
Copy link
Contributor

I actually opened an upstream issue with ruby-core about this:

https://bugs.ruby-lang.org/issues/11904

The use of Thread.exclusive is to prevent a potentially multithreaded caller from making concurrent calls to this function.

Just adding an inline mutex doesn't help with that case. If ruby-core decides to go ahead with this, we just need to remove the Thread.exclusive block and potentially provide documentation advice.

@tarcieri tarcieri closed this Dec 29, 2015
@mariovisic
Copy link
Author

@tarcieri interesting, thanks for the link :)

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 this pull request may close these issues.

None yet

2 participants