@kddnewton There is already a PR with both parse.y (from @nobu) and Prism changes: https://github.com/ruby/ruby/pull/11065 I'd be happy to rebase, update that branch and merge any other changes you think are important for Prism.ufuk (Ufuk Kayserilioglu)
@Dan0042 If the proposed method isn't going to raise an exception, then how would one disambiguate between a `nil` result because the collection has a single entry which is `nil` and a `nil` result since the collection has (for example) ...ufuk (Ufuk Kayserilioglu)
Did 3.5-preview1 have the same behaviour? If not, could you bisect between the two releases to find the commit that changed the behaviour?ufuk (Ufuk Kayserilioglu)
From the docs https://docs.ruby-lang.org/en/3.4/Kernel.html#method-i-Integer: > With base zero, string object may contain leading characters to specify the actual base (radix indicator): > ... So, your strings are interpreted as octa...ufuk (Ufuk Kayserilioglu)
retro (Josef Šimánek) wrote in #note-17: > @mame so why to release 4.0 if not causing major breaking changes? Quoting [my answer to this](https://bugs.ruby-lang.org/issues/21657#note-3) from above: > ... that is completely a decisio...ufuk (Ufuk Kayserilioglu)
IMO, ranges should behave the same when `end == Float::INFINITY` and when `end == nil`. They are both practically endless ranges, but nothing normalizes them so that they always behave the same. Maybe `(1..1/0.0)` should be internally tr...ufuk (Ufuk Kayserilioglu)
It seems like the next version of Ruby will be branded as 4.0, but that is completely a decision for @matz to make as he wishes. Ruby version numbers don't follow semantic versioning, so 4.0 doesn't mean that there will be breaking chang...ufuk (Ufuk Kayserilioglu)
There is a configuration file to control which labeled PRs make it into the automated release notes and which ones should be excluded. I can help set that up if it will be helpful.ufuk (Ufuk Kayserilioglu)