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
Each Query currently iterates the whole list of Archetypes. This is bad for scenarios with many archetypes.
Instead each query should ONLY iterate archetypes that fits its description.
Solution
We need some way to map a Query to its Archetypes and a Archetype to its Querys in a decoupled way.
Therefore, we could add a QueryCache to the World that exactly does this mapping and validates the process.
Or as an alternative we put those lists directly into the Query and Archetype. This however would couple the classes to another which is generally not a great idea for refactoring and maintainability reasons.
The text was updated successfully, but these errors were encountered:
Problem
Each Query currently iterates the whole list of Archetypes. This is bad for scenarios with many archetypes.
Instead each query should ONLY iterate archetypes that fits its description.
Solution
We need some way to map a
Query
to itsArchetype
s and aArchetype
to itsQuerys
in a decoupled way.Therefore, we could add a
QueryCache
to theWorld
that exactly does this mapping and validates the process.Or as an alternative we put those lists directly into the
Query
andArchetype
. This however would couple the classes to another which is generally not a great idea for refactoring and maintainability reasons.The text was updated successfully, but these errors were encountered: