I don't have a strong opinion here, but one argument I could see for inclusion in core is to optimize frozen constants, e.g. ```ruby SCHEMA = [ { type: :foo, tags: ["a", "b"] }, { type: :bar, tags: ["c", "d"] }, ... ].deep_...byroot (Jean Boussier)
Eregon (Benoit Daloze) wrote in #note-2: > I think any expression should be allowed and just call `===` on them. Agreed. To me `rescue` is just a shorthand for `rescue e; case e; when ` but that is strangely limited. I suspect rem...byroot (Jean Boussier)
Fix: https://github.com/ruby/json/issues/970 If the parsed exponent overflows a `int32_t` passing it to ryu is incorrect. We could pass it to `rb_cstr_to_dbl` but then Ruby will emit an annoying warning, instead we can coerce to `0.0` ...byroot (Jean Boussier)
I know very little about parser, so perhaps what I'm about to suggest is entirely impossible, but could we refine that warning as to only trigger it if the other interpretation would be valid syntax? e.g.: - `p -1` - Both `p(-1)...byroot (Jean Boussier)
> 3.2: REQUIRED, 3.3: REQUIRED, 3.4: REQUIRED, 4.0: REQUIRED I don't know if this bug actually qualify for 3.3 (and more so 3.2) backport, but in doubt I made the PRs: - 4.0: https://github.com/ruby/ruby/pull/16726 - 3.4: http...byroot (Jean Boussier)