forcing "@nogc" on class destructors

[deadalnix via Digitalmars-d]

On Tuesday, 20 January 2015 at 22:16:31 UTC, Ola Fosheim Grøstad 
wrote:
> On Tuesday, 20 January 2015 at 22:10:36 UTC, deadalnix wrote:
>> That is GC implementation issue, not a language issue. If it 
>> ain't broken, don't fix it.
>
> Efficient GC with compile time safety is a language issue. 
> Current Class allocation and deallocation patterns are making 
> fast collection unlikely IMHO.

Any serious GC can run concurrently (instead of stopping the 
world). That mean any serious GC must be able to handle 
allocations while collecting.

Not only handling these case is unlikely to make the GC any 
slower, but in fact, this is required to make the GC faster.