forcing "@nogc" on class destructors

[via Digitalmars-d]

On Wednesday, 21 January 2015 at 20:15:53 UTC, deadalnix wrote:
> Ok listen, I'm gonna put a full stop to this conversation :
>  - You provide no evidence of your claims.

HAHAHA…

>  - You discard any evidence that contradict your claims without 
> solid argument.

What evidence?

>  - You are constantly shitfting the goalspot using more and 
> more ridiculous claims (like malloc should not be used).

You can batch-allocate, but you need to use an O(1) allocator if 
you want fast memory handling.

> There no point in continuing this discussion.

That's right...

>  - A concurrent GC is not suitable for system languages.

And there is nothing that suggests that it is. Go is not a system 
programming language.