don't reset memory of finalized classes/structs/arrays

[MartinNowak]

No description provided.

[andralex]

Risky but efficient.

[MartinNowak]

Risky but efficient.

Rather not, because it was freed by the GC. And when the men is allocated again you hopefully don't forget to initialize it ;).
We already did it for classes, so this just applies existing behavior to structs and writing to all the reclaimed memory is extremely expensive.

[schveiguy]

finalize_array2 is called by GC, finalize_array I believe is still called by doing delete arr (haven't verified this)

That being said, I still think this change is fine.

[MartinNowak]

But delete ary wasn't resetting memory before #864.

[schveiguy]

Sure, and really, delete frees the memory, so any access to a dangling reference is invalid whether you re-initialize or not.