Charles Waldner
Charles Waldner
So, why not have both? Option B with debug-time assertions, and the option to have transactions that limit which components can be written to. Just throwing it out there.
Does entityx currently not support any form of cache coherency when deleting and re-adding components / entities? (in compile_time branch or master) eg. When deleting an entity does it swap...
Worse performance? Is that just when deleting or is that also when iterating? or all of the above?
Not sure if this is a bug. It looks like CppParser just excludes passing the `-xc++` option to clang if ParseAsCpp is false. I think you can work around it...
Has this issue been resolved? I'm curious what the actual license here is. And, if I'd like to contribute, what's the best way to do so without violating Microsoft's license?...
New to Glew - Please at least add this to the README. Compiling glew without this information is frustrating to say the least.
There appear to be more places in the scripts where this is an issue.
I see that this is a fairly old request, however - I too am looking for something like this.
I'm running into the same issue.
I feel like this is on the right track. If you decide to implement this, it might be nice to have an explicit assignment method as well. `UnallocatedEntity::allocate();` or `EntityManager::create_temporary()`...