API Design: define entities by archetype directly about ecez HOT 3 CLOSED

each archetype should implement an interface
we can then have an array of these interfaces and then we can make some operations O(1) i.e hasComponent and getComponent etc...

The std.mem.Allocator is a good place to start for dynamic dispatch: https://github.com/ziglang/zig/blob/master/lib/std/mem/Allocator.zig

from ecez.

The restriction of only allowing predefined archetypes can be removed by using the interface idea

Queries can be processed on compile time using comptime and itnerfaces can be used to do partial type erasure needed to combine different archetypes!

from ecez.

Resolved by PR #30

from ecez.