On 28 June 2026 15:25:53 BST, "Alex Pătrănescu" <[email protected]> wrote: >The name is still open, but I am not sure about using "container" as the >final name. >To me, it does not fully match the design I have in mind: a graph of >symbol-owning packages/modules where code running in one module can only >see its own symbols and the symbols from its declared dependencies. > > ... > >As I mentioned, these runtime modules could map naturally over Composer >packages and their required dependencies.
OK, then I don't know what problem you're trying to solve. It sounds like a lot of disruption to a package ecosystem which already works perfectly well. The WordPress use case does not need to declare a hierarchy of modules; it needs to create a single boundary around an arbitrary set of code, which might or might not happen to be a fully-populated vendor directory. Rowan Tommins [IMSoP]
