Ruby Issue Tracking System

05/28/2025

07:44 AM Ruby Bug #21378: variable pinning does not look for method arguments

It's the same with parse.y:
```
$ ruby -v --parser=parse.y -e 'def x?(y, z) = y in { x: ^z }'
ruby 3.5.0dev (2025-... Eregon (Benoit Daloze)

07:38 AM Ruby Bug #21377: core Set#inspect does not use inherited class name

Agreed, if the `inspect` shows the class name, it should show `obj.class.name`, not some superclass which would be ve... Eregon (Benoit Daloze)

05/26/2025

10:00 AM Ruby Feature #21365: Add `Namespace#eval`

`ns.eval "self"` would be the Namespace "main" object, not the `Namespace` instance itself, so `instance_eval` would ... Eregon (Benoit Daloze)

05/23/2025

02:08 PM Ruby Feature #21359: Introduce `Exception#cause=` for Post-Initialization Assignment

`msgpack` doesn't seem to handle recursive data structures:
```
irb(main):003> a=[]
=> []
irb(main):004> a<<a
=>... Eregon (Benoit Daloze)

01:58 PM Ruby Feature #21365: Add `Namespace#eval`

Yep, agreed it'd be far more convenient for testing Namespace.
matheusrich (Matheus Richard) wrote in #note-1:
> ... Eregon (Benoit Daloze)

05/22/2025

08:53 PM Ruby Bug #21362: Namespace: Inline method caches poisoned with builtins

Yeah such builtin/core Ruby files clearly need to be loaded and executed in the root namespace from a performance POV... Eregon (Benoit Daloze)

08:00 PM Ruby Feature #21359: Introduce `Exception#cause=` for Post-Initialization Assignment

ioquatix (Samuel Williams) wrote in #note-2:
> Yes, in Async, I want to set the cause of an exception before raising... Eregon (Benoit Daloze)

10:15 AM Ruby Feature #21359: Introduce `Exception#cause=` for Post-Initialization Assignment

Do you have real-world examples where you would use this, e.g. in gems? Eregon (Benoit Daloze)

07:53 PM Ruby Feature #21361: Set execution file and line

I'm not sure we want to encourage generating Ruby code (generated code in many cases is pretty bad IMO, e.g. huge met... Eregon (Benoit Daloze)

05/19/2025

08:25 PM Ruby Bug #21348: Should Tracepoint track retry as another "call" event?

I agree with the OP that `:call` shouldn't trigger a second time here, since there is only one call to `foo`.
`retry... Eregon (Benoit Daloze)