mirror of
https://github.com/bevyengine/bevy
synced 2024-11-10 07:04:33 +00:00
b911a005d9
# 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> |
||
|---|---|---|
| .. | ||
| bevy_app | ||
| bevy_asset | ||
| bevy_audio | ||
| bevy_core | ||
| bevy_derive | ||
| bevy_diagnostic | ||
| bevy_dylib | ||
| bevy_dynamic_plugin | ||
| bevy_ecs | ||
| bevy_gilrs | ||
| bevy_gltf | ||
| bevy_input | ||
| bevy_internal | ||
| bevy_log | ||
| bevy_macro_utils | ||
| bevy_math | ||
| bevy_pbr | ||
| bevy_reflect | ||
| bevy_render | ||
| bevy_scene | ||
| bevy_sprite | ||
| bevy_tasks | ||
| bevy_text | ||
| bevy_transform | ||
| bevy_ui | ||
| bevy_utils | ||
| bevy_wgpu | ||
| bevy_window | ||
| bevy_winit | ||