davier

I see two goals in this RFC: 1. fine-grained runtime checked queries in WorldCell 2. make "overlayed" changes to a WorldCell Goal 1 seems reasonable, and if I remember correctly...

> > Could you provide examples that require the world overlays? > > Arbitrary callbacks which add/remove entities or components, even while borrows to disjoint components are held elsewhere. My...

While this PR fixes one issue with cache invalidation, there is still another issue causing exponential recursion. I'll detail it here since I haven't been able to solve it yet....

I had the same use case, and my solution was to propose a way to extend materials in #10816. That allowed me to add an instance vertex buffer with the...

> I made a proof of concept that involved automatic subdivision of Z-space evenly among its children (and their children, and so on). That was tried in #1211 and the...

Entities are part of stacking contexts. In the default case a context contains an entity and its children, but it can get arbitrarily complex using the `ZIndex::Auto` property. Stacking contexts...

I think using `enum`s is problematic since they are static, we should probably support a dynamic number of layers. I would even argue for a total ordering between every Sprite...

Would it be possible for the scheduler to calculate the number of `EventReader` and store it in `Events`? If so, we could copy that number into any new `EventInstance`, decrement...

> don't you still need a way for each consumer to individually track what events they've seen? Event readers already do this by saving the event counter, what I suggested...

> There's another ongoing discussion where one of proposals replaces the flag by the generation number field exactly to solve that kind of issue, events won't be lost in that...