5f4b5a37f1
# Objective Allow resources to be accessed soundly by `QueryData` and `QueryFilter` implementations. This mostly works today, and is used in `bevy-trait-query` and will be used by #16810. The problem is that the access is not made visible to the executor, so it would be possible for a system with resource access in a query to run concurrently with a system that accesses the resource with `ResMut`, resulting in Undefined Behavior. ## Solution Define calling `add_resource_read` or `add_resource_write` in `WorldQuery::update_component_access` to be a supported way to declare resource access in a query. Modify `QueryState::new_with_access` to check for resource access and report it in `archetype_component_acccess`. Modify `FilteredAccess::is_compatible` to consider resource access conflicting even on queries with disjoint filters. |
||
|---|---|---|
| .. | ||
| access.rs | ||
| builder.rs | ||
| error.rs | ||
| fetch.rs | ||
| filter.rs | ||
| iter.rs | ||
| mod.rs | ||
| par_iter.rs | ||
| state.rs | ||
| world_query.rs | ||