Ruby Issue Tracking System

08/26/2025

02:02 AM Ruby Misc #21385: Namespace: Suggesting a rename

I'll work on renaming `Namespace` to `Ruby::Box` after this: https://github.com/ruby/ruby/pull/13454 tagomoris (Satoshi Tagomori)

06/30/2025

12:54 PM Ruby Misc #21385: Namespace: Suggesting a rename

My idea that popped up recently is, "Ruby Box", referenced as `Ruby::Box`. tagomoris (Satoshi Tagomori)

05/20/2025

01:15 PM Ruby Bug #21341: `Namespace is not a module (TypeError)` without enabling the namespace

I want to let Matz determine how to handle this problem :D tagomoris (Satoshi Tagomori)

05/14/2025

01:08 AM Ruby Feature #21335: Namespaces should be present in the backtrace

The `ns_id` seems good to be shown in backtrace (I'm unsure about this format is good or not):
```
foo.rb:7:in namespace(1) 'Foo.test'
``` tagomoris (Satoshi Tagomori)

05/13/2025

12:00 PM Ruby Bug #21330: Namespace: Class and Module frozen status is not namespaced

The frozen flag is what I missed. I think we should move the flag to `rb_classext_t`. tagomoris (Satoshi Tagomori)

05/12/2025

01:07 PM Ruby Feature #21311 (Open): Namespace on read (revised)

byroot (Jean Boussier) wrote in #note-75:
> > Please open another ticker for further problems, issues, bugs, etc.
> ...
I had a plan to add CI configuration to add `RUBY_NAMESPACE=1` checks and I thought it would not be a part of this.... tagomoris (Satoshi Tagomori)

12:42 PM Ruby Feature #21311 (Closed): Namespace on read (revised)

I've merged the change into master. So, let me close this issue.
Please open another ticker for further problems, issues, bugs, etc. tagomoris (Satoshi Tagomori)

05/11/2025

03:05 PM Ruby Feature #21311: Namespace on read (revised)

fxn (Xavier Noria) wrote in #note-70:
> Maybe you have the C code in your head, I am looking at it as a Ruby programmer would. I have one object reference, and I pass it in method call, no namespace-level constant resolution involved in... tagomoris (Satoshi Tagomori)

02:50 PM Ruby Feature #21311: Namespace on read (revised)

fxn (Xavier Noria) wrote in #note-68:
> @tagomoris when I said that (1) would break Ruby semantics I meant that **in the same namespace** you would have two objects with the same ID and different state. That does not happen as far as I ... tagomoris (Satoshi Tagomori)

02:32 PM Ruby Revision b94df81b (git): RUBY_TYPED_WB_PROTECTED should be specified with write barrier protection on this object.

https://github.com/tagomoris/ruby/pull/7
RUBY_TYPED_FREE_IMMEDIATELY can be added because namespace_entry_free does no IO nor
things to block. tagomoris (Satoshi Tagomori)