GC has a "barbaric" destroyng model, I think

[Andrey Derzhavin via Digitalmars-d-learn]

On Thursday, 12 February 2015 at 13:11:48 UTC, ketmar wrote:
> sure. but when it comes, for example, for big data structures 
> with
> complex cross-references, you'll inevitably found that you 
> either leaking
> memory, or writing your own half-backed semi-working GC 
> realization.
>
> ah, good luck doing effecient refcounting on slices, for 
> example. and
> they aren't even remotely complex.

Well. What is the trouble if dtors are always (it is garanteed) 
called by GC before their phisical destroying?
It will help to avoid many awkward situations.