[ruby-core:120808] [Ruby master Bug#21094] Module#set_temporary_name does not affect a name of a nested module

Issue #21094 has been reported by andrykonchin (Andrew Konchin).

----------------------------------------
Bug #21094: Module#set_temporary_name does not affect a name of a nested module
https://bugs.ruby-lang.org/issues/21094

* Author: andrykonchin (Andrew Konchin)
* Status: Open
* ruby -v: 3.4.1
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN
----------------------------------------
Wondering whether it's intentional and correct behaviour:

```ruby
m = Module.new
m::N = Module.new
p m::N.name # => "#<Module:0x000000010d0a00b0>::N"

m.set_temporary_name("foo")
p m::N.name # => "#<Module:0x000000010d0a00b0>::N"
```

I would expect that setting `foo` as a temporary name changes `m::N.name` to `foo::N`.



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- [e-mail]
 To unsubscribe send an email to [e-mail]
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/