Go, D, and the GC

[rsw0x via Digitalmars-d]

On Sunday, 4 October 2015 at 17:22:52 UTC, Martin Nowak wrote:
> On Friday, 2 October 2015 at 11:27:12 UTC, Tourist wrote:
>> I know that it has the reputation of being of the simplest 
>> kind. Haven't looked at the code actually (and I wouldn't 
>> understand much even if I did).
>
> Go has a very simple GC itself. It's concurrent, so it trades 
> low latency against performance (write-barriers) and throughput.
> We wouldn't want to force everybody to use write-barriers, but 
> you can avoid creating garbage in D much easier (e.g. map) and 
> we're improving support for deterministic memory management. So 
> while we keep on improving D's GC as well, GC performance is 
> less of a problem in D b/c you have a smaller GC heap.

I still say it's worth investigating a thread-local GC by taking 
advantage of the fact that shared has never really been properly 
fleshed out. This would heavily play to D's TLS by default, and 
preferring message passing over shared data.

Bye.