Proper way to work around `Invalid memory operation`?

[ketmar via Digitalmars-d-learn]

On Monday, 26 September 2016 at 09:43:02 UTC, Nemanja Boric wrote:
> On Sunday, 25 September 2016 at 16:07:12 UTC, Matthias Klumpp 
> wrote:
>> At time, I work around this bug by calling close() manually at 
>> the appropriate time, but this feel like a rather poor 
>> solution.
>>
>> Cheers,
>>     Matthias
>
> That's not a poor solution, but rather a much better solution 
> if you rely on GC to call destructor (which it may or may not 
> do).
yes. i want to stress that there is no *requrement* for GC to 
call dtors. GC which just doesn't is perfectly valid by the specs.