[ruby-core:121952] [Ruby Bug#21318] Namespaces leak with permanent names
Issue #21318 has been reported by fxn (Xavier Noria). ---------------------------------------- Bug #21318: Namespaces leak with permanent names https://bugs.ruby-lang.org/issues/21318 * Author: fxn (Xavier Noria) * Status: Open * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Namespaces are not transparent for this program: ```ruby Module.nesting ``` The nesting is empty or not depending on whether it is being executed under a namespace. -- https://bugs.ruby-lang.org/
Issue #21318 has been updated by fxn (Xavier Noria). Subject changed from Namespaces leak with permanent names to Namespaces leak with Module.nesting Namespaces are not transparent for this program: ```ruby Module.nesting ``` The nesting is empty or not depending on whether it is being executed under a namespace. ---------------------------------------- Bug #21318: Namespaces leak with Module.nesting https://bugs.ruby-lang.org/issues/21318#change-113070 * Author: fxn (Xavier Noria) * Status: Open * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Namespaces are not transparent for this program: ```ruby Module.nesting ``` The nesting is empty or not depending on whether it is being executed under a namespace. -- https://bugs.ruby-lang.org/
Issue #21318 has been updated by Eregon (Benoit Daloze). Complete reproducer: ``` $ RUBY_NAMESPACE=1 ruby -ve 'p Module.nesting; ns = Namespace.new; File.write "ns.rb", "p Module.nesting"; ns.require "./ns"' ruby 3.5.0dev (2025-05-10T07:50:29Z namespace-on-read-.. bd4f57f96b) +PRISM [x86_64-linux] ruby: warning: Namespace is experimental, and the behavior may change in the future! See doc/namespace.md for know issues, etc. [] [#<Namespace:24,user,optional>] ``` ---------------------------------------- Bug #21318: Namespaces leak with Module.nesting https://bugs.ruby-lang.org/issues/21318#change-113097 * Author: fxn (Xavier Noria) * Status: Open * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Namespaces are not transparent for this program: ```ruby Module.nesting ``` The nesting is empty or not depending on whether it is being executed under a namespace. -- https://bugs.ruby-lang.org/
Issue #21318 has been updated by tagomoris (Satoshi Tagomori). Assignee set to tagomoris (Satoshi Tagomori) ---------------------------------------- Bug #21318: Namespaces leak with Module.nesting https://bugs.ruby-lang.org/issues/21318#change-115533 * Author: fxn (Xavier Noria) * Status: Open * Assignee: tagomoris (Satoshi Tagomori) * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Namespaces are not transparent for this program: ```ruby Module.nesting ``` The nesting is empty or not depending on whether it is being executed under a namespace. -- https://bugs.ruby-lang.org/
Issue #21318 has been updated by tagomoris (Satoshi Tagomori). Status changed from Open to Closed Now `Module.nesting` doesn't return its box information in a box. ``` MBA:build s-tagomori$ RUBY_BOX=1 ./exe/ruby -v ruby 4.0.0dev (2025-12-09T12:29:36Z box-news-documents.. c998717de8) +PRISM [arm64-darwin24] MBA:build s-tagomori$ RUBY_BOX=1 ./exe/ruby -ve 'p Module.nesting; ns = Ruby::Box.new; File.write "ns.rb", "p Module.nesting"; ns.require "./ns"' ruby 4.0.0dev (2025-12-09T12:29:36Z box-news-documents.. c998717de8) +PRISM [arm64-darwin24] ./exe/ruby: warning: Ruby::Box is experimental, and the behavior may change in the future! See doc/language/box.md for known issues, etc. [] [] MBA:build s-tagomori$ ``` ---------------------------------------- Bug #21318: Namespaces leak with Module.nesting https://bugs.ruby-lang.org/issues/21318#change-115543 * Author: fxn (Xavier Noria) * Status: Closed * Assignee: tagomoris (Satoshi Tagomori) * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Namespaces are not transparent for this program: ```ruby Module.nesting ``` The nesting is empty or not depending on whether it is being executed under a namespace. -- https://bugs.ruby-lang.org/
participants (3)
-
Eregon (Benoit Daloze) -
fxn (Xavier Noria)
-
tagomoris (Satoshi Tagomori)