Not yet. The documentation change that landed is the right amount for now. We may remove this someday, but this is not the moment. I approved `Thread::Backtrace::Location#source_range` in [#22212](https://bugs.ruby-lang.org/issues/222...matz (Yukihiro Matsumoto)
The heuristic is acceptable. Nothing user visible changes here, so choosing where the cutoff sits is an implementation decision, and the measurements in this ticket are more than enough basis for it. Please go ahead with the 128 byte cut...matz (Yukihiro Matsumoto)
I have no objection to the direction. Finding a delimiter is where a parser begins, and a zero copy buffer that cannot do it stops being zero copy at the first `&`. Please work out the design with @ioquatix, who is in charge of `IO::B...matz (Yukihiro Matsumoto)
Please leave this implementation defined. Other implementations should be free to behave differently. [#note-1](https://bugs.ruby-lang.org/issues/22230#note-1) makes the case well. The `IOError` is a consequence of CRuby having a char...matz (Yukihiro Matsumoto)
I agree with the direction, and I agree these should be Fiber-local. What I am not ready to decide is the rule for cases like the one in [#note-13](https://bugs.ruby-lang.org/issues/22216#note-13). Reading `$1` after `e.next` is code ...matz (Yukihiro Matsumoto)
Please go ahead with this approach. Relying on an undocumented bit is not ideal, but the failure mode decides it for me: if the bit ever stops working, we are back to today's 260 character limit, not broken. That is a cheap downside for ...matz (Yukihiro Matsumoto)
I approve the direction. Ractors were designed for exactly the workloads where they currently lose to `fork`, and closing that gap is worth an architectural change of this size. The numbers in section 4 are convincing, and keeping single...matz (Yukihiro Matsumoto)
I approve introducing `#syntax_tree`, and I like the name. Please land it as an experimental feature as you propose in [#note-27](https://bugs.ruby-lang.org/issues/21795#note-27). On the prism version mismatch, I choose your approach:...matz (Yukihiro Matsumoto)
Accepted, including the incompatibilities in section 7. Asking "did you create this?" instead of "are you the main Ractor?" is the right question, and Ractor is experimental precisely so that we can make this kind of correction. On cl...matz (Yukihiro Matsumoto)