Require read-only queries in QueryState::par_iter
#8832
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
The method
QueryState::par_iter
does not currently force the query to be read-only. This means you can unsoundly mutate a world through an immutable reference in safe code.Solution
Use read-only versions of the
WorldQuery
types.Migration Guide
The function
QueryState::par_iter
now forces any world accesses to be read-only, similar to howQueryState::iter
works. Any code that previously mutated the world using this method was unsound. If you need to mutate the world, usepar_iter_mut
instead.