dyn_array but more anal about the contents of the remaining capacity (always enforcing that extra space is 0'd out, or just that all erased space is cleared) and, perhaps, maintained capacity is always +1'd for a terminator.
It would really need to be based off dyn_array, but not use the same API or backend. Vectors and strings really have different needs and use cases, so they are going to end up diverging/specializing quickly.
That will make maintenance a bit of a pain, but hey, dyn_array's really only had one issue so far.
dyn_array but more anal about the contents of the remaining capacity (always enforcing that extra space is 0'd out, or just that all erased space is cleared) and, perhaps, maintained capacity is always +1'd for a terminator.
It would really need to be based off dyn_array, but not use the same API or backend. Vectors and strings really have different needs and use cases, so they are going to end up diverging/specializing quickly.
That will make maintenance a bit of a pain, but hey, dyn_array's really only had one issue so far.