Transitioning to 2.0

[Yelnats321]

I am currently in the process of rewriting EntityPlus! One of the issues is how to transition this repository to the new version. As this is a ground-up rewrite, I am not sure what the correct approach is. I also want to push to the repo when I have a working, mostly stable interface, and it will probably be a single commit that entirely changes the code. It may not be as fast as intended, but featureful enough to use and additional optimization will be added without altering the interface (ideally).

I am not sure if this is the best way to do this. If you have any suggestions on how to transition to this new rewritten version, please let me know!

If you have any features you are interested in, check out the other issues, especially #22 and see if they are covered there. If not, please let me know.

[cppmadguy]

Hello ! I am currently searching for a header only ECS and Entity+ seem to fit my use case. Have you finished the rewrite of your library ? (It has been in rewrite for two years now...)Thanks you for your work anyway !! I would suggest the use of plf::colony instead of vectors, this would improve performance even more because vectors are not great for faster erase/inserts. you can find it at: https://plflib.org/colony.htm, it is header only. The wrapping of the function .reserve(), .shrink_to_fit(), .trim(), of plf::colony would benefit the end user. I am going to try the changes, but I am not an experienced c++ programmer (yet).

[Yelnats321]

Hi! I do have an idea of a rewrite in mind, and being able to specify a container was part of my goal. Unfortunately, real life has eaten up most of my programming time. I would consider this project on a hiatus until I personally have a need for an entity component system, in which case I would develop my rewrite further. It exists in a half baked state right now, but I don't find it acceptable to publish. Thanks for the kind words.

[cppmadguy]

Gonna try the C++17 branch then.