> But the problem still stands: you can't know just by looking at Ruby code (sans type hints or JIT profiles) whether a given method might access the caller's frame in "special" ways. I don't want to derail the discussion too much, bu...byroot (Jean Boussier)
> Updates to backref and lastline are visible across threads and already can lead to concurrency issues even on CRuby. I've always considered this a bug. If possible they should definitely be scoped to the current thread (or rather fi...byroot (Jean Boussier)
The Range Marshal compat dumper would allocate an Object with no size information, hence get a 32B slot with enough space for 2 ivars, then insert 3 ivars causing it to spill. This isn't a big problem, but somewhat shows that the interf...byroot (Jean Boussier)
If `ruby2_keywords` is deprecated, I'll also likely drop support for 2.x rubies in a bunch of gems. I suppose there isn't much reason to keep it, for a while `ruby2_keywords` was the most efficient way to do blind delegation, but sinc...byroot (Jean Boussier)
Based on the data you've provided, I'm pretty convinced that bumping the limit to at least ~128B would make a lot of sense. We could also have a different limit depending on the status of the source string. If the source string is alr...byroot (Jean Boussier)
byroot (Jean Boussier)08:44 PM Ruby Bug #22216: Regexp backref and IO lastline are incompatible with Ractor