alanwu (Alan Wu) wrote in #note-1: > > If it is preferable to specify the cache size via an environment > ... I implemented support for specifying the cache size: https://github.com/ruby/ruby/pull/19509 However, it results in assert...jeremyevans0 (Jeremy Evans)
In case it assists debugging, the example works correctly in Ruby 3.0 and 3.1 (`NameError`) and fails in Ruby 3.2 and 3.3 (SEGV). So it broke between Ruby 3.1 and 3.2.jeremyevans0 (Jeremy Evans)
The shape redblack cache mmaps 384MB of memory at startup. There is currently no way to configure the amount of memory used. The code already handles an mmap failure cleanly. I would like a way to skip the mmap attempt, and the simple...jeremyevans0 (Jeremy Evans)
shugo (Shugo Maeda) wrote in #note-1: > As I commented in https://github.com/ruby/ruby/pull/19474#pullrequestreview-5609342827, with the PR change, `==` UnboundMethods can bind to non-`==` Methods: > ... I think the previous behavior w...jeremyevans0 (Jeremy Evans)
When a `Method` is created using `UnboundMethod#bind` and `#super_method`, the order in which the `#bind` and `#super_method` were applied could result in `Method` objects that were considered unequal. I believe we should have the inv...jeremyevans0 (Jeremy Evans)
@shugo Sorry for the confusion. I rebased the PR to fix conflicts and added a few new commits: 1. Expose a minimal internal C-API for WeakMap 2. Make the refinement module iclass cache weak so it doesn't leak memory 3. Add weak cach...jeremyevans0 (Jeremy Evans)
shugo (Shugo Maeda) wrote in #note-6: > Since `super` from a refinement method now skips the other refinements, Since Ruby 2.7, `super` in a refinement method does not skip other refinements that are in scope at the point of the `sup...jeremyevans0 (Jeremy Evans)
* [Feature #22309] Allow super in a module method to work if method was called by refinement method super (jeremyevans0) * From Ruby 2.4-4.0, `super` has been allowed, but used the wrong method lookup, so it generally resulted in a `N...jeremyevans0 (Jeremy Evans)