Implement QueryData for &Archetype
#12393
Labels
A-ECS
Entities, components, systems, and events
A-Networking
Sending data between clients, servers and machines
C-Feature
A new feature, making something new possible
Comments
urben1680
added
C-Feature
alice-i-cecile
added
A-ECS
|
I've seen this type of pattern used for efficient networking-based serialization and deserialization of entities. |
github-merge-queue bot
pushed a commit
that referenced
this issue
Mar 29, 2024
# 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]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the feature request
&Archetypeis a reference that can be accessed withEntityRefandEntityMutin a query. These latter two however hurt parallization when queried. If one does that only to get&Archetype, that restriction is needless as the archetype reference alone does not require further access to the component data.It would make sense to offer this type as a
QueryDatathat can also be freely added to a query withQuery::transmute_lense.Also, since the number of archetypes a query accesses is most likely much smaller than the number of matched entites, one could consider giving
Querya new method that returns an Iterator over&Archetypes.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: