GC being too eager?

[Paulo Pinto]

On Thursday, 10 April 2014 at 10:37:58 UTC, Rene Zwanenburg wrote:
> On Thursday, 10 April 2014 at 09:24:51 UTC, Paulo Pinto wrote:
>> In a toy project I am working on with D v2.065, I came to the 
>> following situation:
>>
>> Node path = solver.find (map, start, end);
>> if (path !is null) {
>>    path.writeContents();  <-- Access Violation
>> }
>>
>> Apparently between the test and trying to use the class, the 
>> reference becomes null.
>>
>> Quite strange in a single threaded application.
>>
>> Any idea what might be happening or should I delve into 
>> assembly?
>>
>> --
>> Paulo
>
> Can you post writeContents?

Sure, but only today's evening. At work now.

This is a simple A* search program I was porting from C++ to D, 
and I plan to make it visible on Github anyway.

But it shouldn't be related to writeContents, I guess, as the 
access violation takes place regardless of the operation I try to 
apply to path.


--
Paulo