Storing arrays in large dynamic buffers

[popcron]

Right now with how arrays are implemented for entities, if there are 20 entities with a char array, thats 20 unique array instances (allocations).

This issue is for refactoring how they're stored so that a single giant buffer is created for each array type. And when an array is created on an entity, a region from the buffer is consumed. Letting those 20 entities still have their own array, but the underlying allocation is a single one.

This gives them these qualities:

• arrays could be acessed more efficiently
• significantly less memory fragmentation
• slower to modify length

Some more details on the refactor:

• arrays will behave like lists
  • when capacity needs to increase, other regions will be shifted
• maybe new constructs to contain arrays, because their region within the buffer may change as its passed around
• the type used for accessing the array will likely be a ref struct

[popcron]

This strategy could also be applied to the references lists on each entity

[popcron]

storing information for where an array starts and how long slowed me down because i didnt consider that. if the array<value> is to be removed from a slot, there has to be a way for a slot to describe the range of each of its arrays. if its a fixed buffer of ints, that can be quite a big value type pull. maybe this could be skipped...