* [ruby-core:120808] [Ruby master Bug#21094] Module#set_temporary_name does not affect a name of a nested module
@ 2025-01-28 11:19 andrykonchin (Andrew Konchin) via ruby-core
2025-01-28 18:19 ` [ruby-core:120810] " eileencodes (Eileen Uchitelle) via ruby-core
0 siblings, 1 reply; 2+ messages in thread
From: andrykonchin (Andrew Konchin) via ruby-core @ 2025-01-28 11:19 UTC (permalink / raw)
To: ruby-core; +Cc: andrykonchin (Andrew Konchin)
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 -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
* [ruby-core:120810] [Ruby master Bug#21094] Module#set_temporary_name does not affect a name of a nested module
2025-01-28 11:19 [ruby-core:120808] [Ruby master Bug#21094] Module#set_temporary_name does not affect a name of a nested module andrykonchin (Andrew Konchin) via ruby-core
@ 2025-01-28 18:19 ` eileencodes (Eileen Uchitelle) via ruby-core
0 siblings, 0 replies; 2+ messages in thread
From: eileencodes (Eileen Uchitelle) via ruby-core @ 2025-01-28 18:19 UTC (permalink / raw)
To: ruby-core; +Cc: eileencodes (Eileen Uchitelle)
Issue #21094 has been updated by eileencodes (Eileen Uchitelle).
This seems like a bug to me because if you set the temp name before creating `N` it works as you expected. Opened a PR https://github.com/ruby/ruby/pull/12658
----------------------------------------
Bug #21094: Module#set_temporary_name does not affect a name of a nested module
https://bugs.ruby-lang.org/issues/21094#change-111678
* 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 -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-01-28 18:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-01-28 11:19 [ruby-core:120808] [Ruby master Bug#21094] Module#set_temporary_name does not affect a name of a nested module andrykonchin (Andrew Konchin) via ruby-core
2025-01-28 18:19 ` [ruby-core:120810] " eileencodes (Eileen Uchitelle) via ruby-core
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).