On Friday, 11 April 2014 at 11:25:16 UTC, Paulo Pinto wrote:
This was only to show you how to reproduce the error.
On my application I use Array as a backing store for a
BinaryHeap used to store the nodes that are available on the A*
open list.
If this usage of Array is correct and the destroy method is
misbehaving, I can create a bug for it.
I assume Array should manage its own memory but not touch the
memory that belongs to reference types stored on it. At least
the documentation doesn't say otherwise.
Yes, it's bug. Trivial to fix too. Please file it.
