The "realloc" opperation, which is changing the slice's length, behaves as follows:

If the goal is to make the array grow, then it may or may not relocate depending on several factors. In any-case, *regardless* of *all* factors, any new element that come from changing the length will be initialialized to T.init (0). Furthermore, it will *never* overwrite any one else's data. So in case of array growth, corruption is impossible, and new elements are initialized to 0.

Shrinking is *always* in place: this is because nothing actually happens, the slice is only "re-sliced". No data is changed ever.