bevy/crates/bevy_ecs/src/system
MinerSebas b911a005d9 Mention creation of disjoint Querys with Without<T> in conflicting access Panic (#2413)
# Objective

Beginners semi-regularly appear on the Discord asking for help with using `QuerySet` when they have a system with conflicting data access.
This happens because the Resulting Panic message only mentions `QuerySet` as a solution, even if in most cases `Without<T>` was enough to solve the problem.

## Solution

Mention the usage of `Without<T>` to create disjoint queries as an alternative to `QuerySet`

## Open Questions

- Is `disjoint` a too technical/mathematical word?
- Should `Without<T>` be mentioned before or after `QuerySet`?
  - Before: Using `Without<T>` should be preferred and mentioning it first reinforces this for a reader.
  - After: The Panics can be very long and a Reader could skip to end and only see the `QuerySet`


Co-authored-by: MinerSebas <66798382+MinerSebas@users.noreply.github.com>
2021-07-01 20:20:11 +00:00
..
commands.rs small ecs cleanup and remove_bundle drop bugfix (#2172) 2021-05-18 19:25:57 +00:00
exclusive_system.rs Optional .system (#2398) 2021-06-27 00:40:09 +00:00
function_system.rs Optional .system(), part 3 (#2422) 2021-07-01 19:09:34 +00:00
mod.rs Optional .system(), part 3 (#2422) 2021-07-01 19:09:34 +00:00
query.rs [ecs] implement is_empty for queries (#2271) 2021-06-02 20:50:06 +00:00
system_chaining.rs Improve bevy_ecs::system module docs (#1932) 2021-04-15 20:36:16 +00:00
system_param.rs Mention creation of disjoint Querys with Without<T> in conflicting access Panic (#2413) 2021-07-01 20:20:11 +00:00
system.rs Cargo fmt with unstable features (#1903) 2021-04-21 23:19:34 +00:00