zverok (Victor Shepelev) wrote in #note-5: > Just noticed that on the latest `master` subclasses `#inspect` didn't change (unlike what @matz suggests here: https://bugs.ruby-lang.org/issues/21389#note-3): > ... Yes, this is deliberate ...jeremyevans0 (Jeremy Evans)
Earlopain (Earlopain _) wrote in #note-12: > I ran this change over code available on rubygems and it only impacts 37 files which go syntax invalid with this. If I take out duplicate vendorered files, it is down to just 7. If it's no...jeremyevans0 (Jeremy Evans)
Is there a reason to prefer `vX.Y.Z` over `X.Y.Z`? The `v` tag prefix does seem more popular, though both are widely used. The historical reason for using `_` in tags also applies to the reason the `v` prefix is used. If we are switching...jeremyevans0 (Jeremy Evans)
bkuhlmann (Brooke Kuhlmann) wrote in #note-18: > Any chance this could be fixed and included in time for the Ruby 4.0.0 release? This is already implemented in Ruby 4.0.0-preview2 for Proc, Method, and UnboundMethod, but not Binding.jeremyevans0 (Jeremy Evans)
Eregon (Benoit Daloze) wrote in #note-10: > FWIW it sounds quite bad contention-wise to use a global queue/stack (EDIT: and a stack is worse than a queue re contention) for connections, at least for the case `#connections >= #threads`. ...jeremyevans0 (Jeremy Evans)
I'm in favor of a LIFO-alternative to `Thread::Queue` and `Thread::SizedQueue` in core. However, it should not have queue in the name, as queue implies FIFO behavior. It should have stack in the name, as stack implies LIFO behavior. `Thr...jeremyevans0 (Jeremy Evans)
Thank you for the report. This is a bug in the allocationless anonymous splat optimization in Ruby 3.4, still present in the master branch. I'll work on a fix.jeremyevans0 (Jeremy Evans)
thyresias (Thierry Lambert) wrote in #note-8: > jeremyevans0 (Jeremy Evans) wrote in #note-7: > ... Updating just the title is fine. I don't think you need to open a new bug report. > As an aside, you said about the encoding of the ...jeremyevans0 (Jeremy Evans)
thyresias (Thierry Lambert) wrote in #note-6: > Thank you. I agree with your analysis of the bug origin: should I edit this to re-qualify it as "inconsistent Regexp interpolation behavior", and update the example code using your example...jeremyevans0 (Jeremy Evans)