Skip to content

Add archetype cache to queries  #53

@cart

Description

@cart

Currently hecs queries iterate over all archetypes to check if that archetype matches the query. For a small number of archetypes, this is probably faster, but it will get more expensive as the number of archetypes (and/or number of components per archetype) gets larger. for a game engine (which will have many archetypes), it makes sense to have a cache. we could then invalidate the cache whenever an archetype is added/removed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-ECSEntities, components, systems, and eventsC-FeatureA new feature, making something new possible

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions