Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
ljm
8 days ago
|
parent
|
context
|
favorite
| on:
Ruby 3.5 Feature: Namespace on read
Realistically it would be FooBar::Record and ns1::FooBar::Record too, unless gems start replacing their top level module FooBar with FooBar = Namespace.new.
And why would you bother doing that when it would be a breaking change?
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search:
And why would you bother doing that when it would be a breaking change?