Go 1.5

[Ola Fosheim Grøstad via Digitalmars-d-announce]

On Saturday, 19 September 2015 at 08:36:51 UTC, thedeemon wrote:
> full heap every time. And that leads to different usage pattern 
> where GC heap should remain small and GC allocation rate low.

Please, let's stop pretending you only have to scan the GC heap. 
You have to scan all pointers that somehow can lead to something 
that can lead to something... that points into the GC heap.

To get out of that you need a language constructs that create a 
verified separation between pointers that can and pointers that 
cannot reach GC pointers.

That's very hard to do, especially since D does not have GC 
pointers.