post on using go 1.5 and GC latency

[via Digitalmars-d-learn]

On Saturday, 22 August 2015 at 12:48:31 UTC, rsw0x wrote:
> The problem with D's GC is that there's no scaffolding there 
> for it, so you can't really improve it.
> At best you could make the collector parallel.
>
> If I had the runtime hooks and language guarantees I needed I'd 
> begin work on a per-thread GC immediately.

If you had a fiber local reference type and some guarantees 
related to that, you probably could do a per-fiber GC and collect 
when fibers are waiting.