Had an idea for a while to specify the underlying storage of a component (for example an unordered_map may be more performant for some data sets). This would be done by supplying a component_list with an unordered<T> as a template argument, which seems like a very clean way of doing it, but might be hard to implement.
On a similar vein, add a not option for get_entities and for_each, so one can ask for specific tags/components and also specify which tags/components not to have. So something like for_each<Position, Player, not<Inactive>> would fetch every player+position that does not have the Inactive tag. Not restricted to tags, could be components too.
Had an idea for a while to specify the underlying storage of a component (for example an
unordered_mapmay be more performant for some data sets). This would be done by supplying acomponent_listwith anunordered<T>as a template argument, which seems like a very clean way of doing it, but might be hard to implement.On a similar vein, add a
notoption forget_entitiesandfor_each, so one can ask for specific tags/components and also specify which tags/components not to have. So something likefor_each<Position, Player, not<Inactive>>would fetch every player+position that does not have theInactivetag. Not restricted to tags, could be components too.