-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
Drop dependency on mutex_m
#49674
Drop dependency on mutex_m
#49674
Conversation
It used to be stdlib but is being extracted in modern rubies. Overall its usefulness is dubious. In all cases it is included in Rails, it's only for the `synchronize` method, but end up exposing a dozen other useless methods. In the end just using a Mutex is clearer and simpler. In some cases we can even get away with a single mutex in a constant.
6ffdc2a
to
bcdeea5
Compare
hmm, this hasn't made it into 7.1.2, right? Quite the contrary it is a direct dependency of ActiveSupport: https://github.com/rails/rails/blob/v7.1.2/activesupport/activesupport.gemspec 🤔 |
We don't backport this kind of patches. |
Alright 👍 PS: I only noticed this because our builds on GH Actions started to break since
Still investigating, but will file an issue unless that's clearly something on our end. |
Sounds like a bundler bug. |
Actually, bundler doesn't use mutex_m, so must be something else requiring it early. I recommend editing |
Yeah, that was plan too. Going to test this out shortly. It fails right away with |
I did not edit the I'll open an issue over there asking for a release. |
I'll take care of it, thanks for finding it. |
Ref: rails/spring#703 |
Spring 4.1.2 is out. |
It used to be stdlib but is being extracted in modern rubies.
Overall its usefulness is dubious. In all cases it is included in Rails, it's only for the
synchronize
method, but end up exposing a dozen other useless methods.In the end just using a Mutex is clearer and simpler.
In some cases we can even get away with a single mutex in a constant.