I am positive about the addition of LEB128. But I don't really like K/k because it doesn't remind me of LEB128 at all (though I know we've used L, E, B already). Given that the only case pairs not yet used are k, r, and y, either R (v...matz (Yukihiro Matsumoto)
The column information from `source_location` will be canceled in 4.0. Let us discuss for the future. I think it's a matter of taste. I don't really care much. Matz. matz (Yukihiro Matsumoto)
I'd like to cancel `source_location` to have column information in 4.0, due to this concern. In my personal opinion, I am leaning toward byte index, though. Matz. matz (Yukihiro Matsumoto)
Although last minute, we will cancel this feature in 4.0 because of design ambiguities such as whether to return column positions in bytes or characters as in #21783. Matz. matz (Yukihiro Matsumoto)
Frankly, I should have designed from the beginning that any method that accepts a block should always take a `&blk` argument, but it is impossible to change that now. Considering that it is meaningful to explicitly state that a method...matz (Yukihiro Matsumoto)
We found some gems inherited from Regexp and used instance variables on instances, so they would be broken if all Regexp objects become frozen. I think it's unacceptable for Ruby 4.0. Frankly, I don't think freezing the Regexp objects i...matz (Yukihiro Matsumoto)