tagomoris (Satoshi Tagomori)
- Login: tagomoris
- Email: tagomoris@gmail.com
- Registered on: 09/24/2010
- Last sign in: 05/01/2025
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 17 | 17 |
Reported issues | 5 | 28 | 33 |
Projects
Project | Roles | Registered on |
---|---|---|
Ruby | Committer | 05/08/2025 |
Activity
05/08/2025
-
12:53 PM Ruby Feature #21311: Namespace on read (revised)
- fxn (Xavier Noria) wrote in #note-44:
> Congrats @tagomoris :).
>
> Would you be open to consider having the perm...
05/07/2025
-
02:04 PM Ruby Feature #21311: Namespace on read (revised)
- @fxn
> So, I guess spawning does not create hierarchy. A namespace may not have a pointer to the namespace where i... -
01:48 PM Ruby Feature #21311: Namespace on read (revised)
- I'm sorry that I skipped to make effort to describe the motivation and copied the motivation section from the past ti...
05/06/2025
-
10:01 AM Ruby Feature #21311: Namespace on read (revised)
- fxn (Xavier Noria) wrote in #note-6:
> In Ruby, objects are stored in constants. Conceptually, a constant `X` storin... -
08:00 AM Ruby Feature #21311: Namespace on read (revised)
- fxn (Xavier Noria) wrote in #note-2:
> A few quick questions:
>
> Assuming a normal execution context, nesting at... -
07:46 AM Ruby Feature #21311: Namespace on read (revised)
- @baweaver I don't have strong opinion about adding `namespace` keyword, but having a block parameter on `Namespace.ne...
-
05:16 AM Ruby Feature #21311 (Open): Namespace on read (revised)
- This replaces #19744
## Concept
This proposes a new feature to define virtual top-level namespaces in Ruby. Th... -
05:19 AM Ruby Feature #19744: Namespace on read
- This is replaced by #21311.
Could someone close this?
05/01/2025
-
06:21 AM Ruby Misc #21281: DevMeeting-2025-05-08
- * [Feature #21311] Namespace on read (tagomoris)
* I'm finishing the namespace branch to be ready for merge (disabl...
09/28/2024
-
07:05 AM Ruby Bug #20767 (Closed): VM_ASSERT fails on clear_method_entry_by_id_in_class() under a specific situation
- VM_ASSERT in `clear_method_entry_by_id_in_class()` (vm_method.c) fails when:
* Kernel#require is refined
* Kernel...
Also available in: Atom