about `dry-system` and `Ruby::Box`

Ruby 4.0’s introduction of `Ruby::Box` experimentally means that we will have (eventually) some mechanism of isolating constants; this could be used as part (a low-level part) of a dependency injection system.

Matz’s rationale for releasing it early and, explicitly, leaving higher-level interfaces for later is to iron out kinks and gather feedback from the community.

Does the `dry-system` team intend to be part of that conversation? The gem could both benefit from `Box` and influence its design, or the design of future APIs based on it.

Hi @nachokb, thanks for raising this—it’s certainly an enticing prospect. Right now, I’m not aware of anyone looking into this. I’d welcome anyone in the community who would like to experiment in this space!