Arrays and non-copyable elements

[Steven Schveighoffer]

On 6/7/20 10:07 PM, Stanislav Blinov wrote:
> On Monday, 8 June 2020 at 00:31:10 UTC, Steven Schveighoffer wrote:
> 
>> This is a bug, please file. What is likely happening is that the 
>> template is not moving the data to the underlying C call.
>>
> 
> That is not a bug, it's a shortcoming of garbage-collected arrays. D 
> arrays are not equipped to deal with non-copyable values. The ~= has to 
> expect to copy contents of arr, since at runtime there may be multiple 
> references to it, i.e:

Ah yes, I was not considering the possibility of having to copy the 
existing data, I was only looking at the new value.

So this is not a bug.

It's not going to be easy to use D arrays for dynamic allocation of 
data. What you probably have to do is pre-allocate a large array and 
then assign new values to the elements.

Possibly an array type that destroys the original data via memory 
setting the data to the init value when reallocating would be the only 
way to fix this.

-Steve