Chris Russell

> I'm a fan of passing it as an argument, I'll do that. I'm hesitant to use `Local`s in this case because that's effectively adding another little bit of complexity...

How are you handling parameters like `&Archetypes` and `Query` that have no `Access` but still rely on the structure of the world not changing? That is, a system like ```rust...

A fun thing this would enable is putting `&mut World` inside a `ParamSet` so you can switch between full access and typed parameters. That's not any more powerful than putting...

> I can do that. There wouldn't be any way to use this new functionality without query implementation, so I though I had to provide at least some way to...

For `AnimationEntityMut`: If we allow `IsResource` entities in that query, and then add the three resources used by the `animate_targets` system to the "except" list, is that enough to support...

> For example, in a ScheduleBuildPass #11094 , you're given some `Box`. These systems were already created by someone else and you don't know who created them or what SystemParam...

> In my particular case, I have a `ScheduleBuildPass` that identifies all systems with a SystemParam `SubmissionInfo` that I defined, look at the system sets and some other information, **group**...

> When you call `add_systems`, you also expose and explicitly consent to other people (bevy developers) calling your function, even though the function itself wasn't explicitly defined as `pub`. As...

> * Tried to migrate existing `pipe` and `map` impls, but failed. This PR is pretty robust for most use cases but isn't fully ready for generic code yet. In...

> My goal was to touch the entity and related storage as little as possible, hopefully reducing the cost of these scopes. > If the to-be-scoped entity is the only...