Make component access in the Query abstraction safe about bevy

[cart]

Oooh good news: it turns out I was wrong about the existing safety checks in the query_1 and query_2 example. They will already immediately fail if two mutable archetype accesses collide, the checks arent per-entity. hecs already implement the solution outlined in (2) for us.

So the main question at this point is: "do we want to rely on that behavior or use a legion-style world api".

[Moxinilian]

We should rely on the original behavior in my opinion. Not only is it easier to reason about for users, it’s also less work and does exactly what is needed.

[cart]

closed by a7bab75