You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EntityLocation is a struct that can be accessed with EntityRef and EntityMut in a query. These latter two however hurt parallization when queried. If one does that only to get EntityLocation, that restriction is needless as the location alone does not require further access to the component data.
It would make sense to offer this type as a QueryData that can also be freely added to a query with Query::transmute_lense.
What problem does this solve or what need does it fill?
I have no personal use case, I just noticed that when looking through the docs to answer someone's question, what else than components can be queried. If someone can come up with an actual use case, please share it in this issue.
The text was updated successfully, but these errors were encountered:
# Objective
Fixes#12392, fixes#12393, and fixes#11387. Implement QueryData for
Archetype and EntityLocation.
## Solution
Add impls for both of the types.
---
## Changelog
Added: `&Archetype` now implements `QueryData`
Added: `EntityLocation` now implements `QueryData`
---------
Co-authored-by: Alice Cecile <[email protected]>
Description of the feature request
EntityLocation
is a struct that can be accessed withEntityRef
andEntityMut
in a query. These latter two however hurt parallization when queried. If one does that only to getEntityLocation
, that restriction is needless as the location alone does not require further access to the component data.It would make sense to offer this type as a
QueryData
that can also be freely added to a query withQuery::transmute_lense
.What problem does this solve or what need does it fill?
I have no personal use case, I just noticed that when looking through the docs to answer someone's question, what else than components can be queried. If someone can come up with an actual use case, please share it in this issue.
The text was updated successfully, but these errors were encountered: