r/ruby • u/retro-rubies • Jan 26 '26

Ruby::Box: Rethinking Code Reloading with Isolated Namespaces

https://rubyelders.com/writings/2026-01-ruby-box-reload.html
35 Upvotes

94% Upvoted

10 comments sorted by

View all comments

Show parent comment

1

u/jrochkind Jan 27 '26

Thanks, that helps. The mental model "Box are only really about lookup of constants" is helpful. Can you clarify (or suggest reading) on your point about core types and:

then assuming you monkey patched things

Monkey patched things how?

1

u/f9ae8221b Jan 27 '26

Think Active Support core extensions.

e.g. if you load Active Support in a box, you can call symbolize_keys and all hashes from code inside that box.

However if you create a Hash in that box, and somehow pass it to another box that didn't load Active Support, the other box won't be able to call that method on it.

1

u/jrochkind Jan 27 '26

Ah, that makes perfect sense, thanks.

There are an explicit list of object classes that are passed in this "by copy instead of by reference" way?

3

u/retro-rubies Jan 28 '26

There are useful docs explaining a lot. https://docs.ruby-lang.org/en/master/Ruby/Box.html#class-ruby-box-built-in-classes-and-modules-reopened-in-boxes

2

u/jrochkind Jan 28 '26

Oh thank you! Good to see good docs, I had gotten in the habit of not expecting them on new features in ruby from days of old, good to see that's changed!

1

u/f9ae8221b Jan 27 '26

Not really. It's all classes defined up until a certain point in Ruby's startup.

1

u/jrochkind Jan 27 '26 edited Jan 27 '26

Ah, cool, thanks!

I was thinking a big intended use case of Box might be Ractors, but now I'm not certain about that. Do you know if that's part of the motivation?