I don't think so, the code very explicitly raises in debug mode: ```c if (RTEST(ruby_debug)) rb_raise(rb_eArgError, "%s", mesg); ``` And that has been the case for at least 18 years: https://github.com/byroot/ruby/commit/549c345c...byroot (Jean Boussier)
### Expected behavior If I'm tracking down a problem and suspect an error might be swallowed somewhere, I do run my test case with `RUBYOPT="-d"` (or simply set `$DEBUG = true`. I do expect the program to execute all in the same wa...byroot (Jean Boussier)
* [Feature #22136] `sprintf` shouldn't raise ArgumentError when $DEBUG is set (byroot) * It's the only method I know of with such behavior. * I think it's counter productive, if I run some code with `$DEBUG = true` I expect its beh...byroot (Jean Boussier)
Since Ruby 3.4 ([Feature #20350]) `Symbol#to_s` returns a chilled string, meaning mutating it emits a deprecation warning. I believe it's now time to act on this deprecation, I'd like to request that on Ruby 4.1, `Symbol#to_s` always ...byroot (Jean Boussier)
👍 this is a lot of complex and error prone code to support a deprecated feature. Very little gems ever used `_id2ref` and nowadays it's always advantageously replaced by a WeakMap.byroot (Jean Boussier)
It will mostly likely be in 4.0.6, which will most likely be released in July, but it can always happen that an urgent security release is needed and that 4.0.6 is released in advance without that specific fix.byroot (Jean Boussier)
> How about to introduce String.new_buffer(capacity) That was the original proposal back in [Feature #12024], but `String.new(**)` was considered more composable. Personally, I must say that if we can make the existing API faster,...byroot (Jean Boussier)
I support this. When working with low-level code that need to buffer IOs for parsing, it's very useful to be in control of the buffer size. However what I found is that the overhead of argument handling when calling `String.new(capaci...byroot (Jean Boussier)
* [Feature #22085] `String#to_f` and `Kernel#Float` shouldn't issue out of range warnings * Here is another example of the warning needing to be worked around: https://github.com/ruby/json/pull/1044byroot (Jean Boussier)