Program crash: GC destroys an object unexpectedly

[eugene]

On Thursday, 23 September 2021 at 13:05:07 UTC, Steven 
Schveighoffer wrote:
> UB in C leaves traps for the programmer, similar to this trap 
> you have found in the GC. Where code doesn't do what you are 
> expecting it to do.

There is a difference, though.
As I've already said,
GC is a sort of 'environment',
the code of GC exits by it's own.

In C, no such code is 'inserted' by compiler
into code written by a programmer.

So, in C it is MY (potentially wrong) code.
In D, it is NOT MY code, it is GC.
 From this point of view debugging
*may* be harder (especially by beginners, like me)