StateMachine is abstract class having Index Key and Indexed Component.

Currently Schema extension only supports IEntityComponent

Let’s have nested IEntityIndexKey.Component instead of Indexed, so we can use it same as StateMachine

Maybe we should defer filter update so user can change filter index while iterating

We will have two problem

• If we do it in step engine we will need user to call our engine.
• Filters will not be updated right away.

What about just giving Copy() for FilteredIndices?

It is possible to inspect what EntityDescriptor assigned with Table,
so it should be possible to inspect below

• Direct Group-Component pair to Index list
• Faster and alloc-free FindGroups implementation

There would be more simpler way to define index key and possibly support multi key index

Thinking of multi index query that gives intersection of two query

You can add entity to it and use it for a step engine pipeline, after entity submission it will be cleared, or user can manually clean.

Should we retain filter after cleared? Need to check Svelto implementation…