On Tue, 16 Jun 2015 16:28:53 +0000, Etienne wrote: > To be fair, everything is bug prone until you understand them. GC > finalization is done in a single lock, none of the memory is re-used, so > objects can have their own "destroyed" flags and destroy eachother fine > if the typeinfo issue isn't there.
this is an implementation detail. nothing guarantees that is will stay like that even for one more commit. relying on this means that your code is bugged and can break at any time, without warning. more than that, if user pulled in another GC implementation, completely adhering to specs, your code simply goes nuts, forcing the poor user to guess what's wrong. so as other people already wrote, simply "don't do it". there will be no way to do what you want here until GC requirements in specs will be changed (and this is unlikely to happen).
signature.asc
Description: PGP signature
