It is memory safe, use-after free, double-free, out-of-bounds access errors etc are all prevented by default. Of course there might be edge cases (bugs in the compiler) where a double free bug happens, but this should not be possible at the language level and then is a compiler bug (I fixed a lot of such bugs over the last few months). You can control them via specific compile flags to make it unsafe, but the default is all properly checked.
Race conditions should be prevented by design, but I haven't actually implemented multithreading at all yet, so I would rather not make any statements about it since it's not done.
I also posted the language on reddit and got quite a lot of feedback from it, and now I am redesigning many parts of it since it was a bit messy (static guarantees, that it basically has nothing to do with ECS any more etc).
I don't know what you exactly mean with an "abstract container". But yes the data `Legs` can be used across many different entity types, you can use and store that component in every entity type you would want to.
Under the hood it essentially is just owned composition, so the entity is just a tuple of pointers to its owned data components, nothing more.
Race conditions should be prevented by design, but I haven't actually implemented multithreading at all yet, so I would rather not make any statements about it since it's not done.
I also posted the language on reddit and got quite a lot of feedback from it, and now I am redesigning many parts of it since it was a bit messy (static guarantees, that it basically has nothing to do with ECS any more etc).
I don't know what you exactly mean with an "abstract container". But yes the data `Legs` can be used across many different entity types, you can use and store that component in every entity type you would want to.
Under the hood it essentially is just owned composition, so the entity is just a tuple of pointers to its owned data components, nothing more.