Ruby Issue Tracking System

05/07/2025

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

byroot (Jean Boussier) wrote in #note-24:
> But I'd like to hear about common green path, day to day, use cases, not fringe needs.
Just was reminded of another gem I wrote that utilizes this pattern.
I use it two ways.
1. When I am wr... peter.boling (Peter Boling)

05/06/2025

08:00 PM Ruby Feature #21311: Namespace on read (revised)

Agreed on all points. I have little concept of the complexity of the implementation, and defer to you on that. I think there is value in considering that we can't entirely know how it might be used since we don't have it yet, and that ... peter.boling (Peter Boling)

06:41 PM Ruby Feature #21311: Namespace on read (revised)

byroot (Jean Boussier) wrote in #note-13:
> > Avoiding name conflicts between libraries: Applications can require two different libraries safely which use the same module name.
> ...
One use case for this is to benchmark libraries that d... peter.boling (Peter Boling)

10/03/2023

07:13 AM Ruby Revision 16a97c7b (git): [rubygems/rubygems] 🚨 Rubocop Linting

https://github.com/rubygems/rubygems/commit/2851e051c3 peter.boling (Peter Boling)

07:13 AM Ruby Revision 9ffd659d (git): [rubygems/rubygems] 🐛 Specification of branch or ref with tag is ambiguous

- Specs for GitProxy were incorrect and insufficient
- Specs are now correct and less insufficient
https://github.com/rubygems/rubygems/commit/63d0a8cfd0 peter.boling (Peter Boling)