On Thursday, 17 April 2014 at 18:00:25 UTC, Dicebot wrote:
Such weak @nogc could help to avoid triggering allocations by an accident and encourage usage of output ranges / buffers.
Ok, more like a "lintish" feature of the "remind me if I use too much of feature X in these sections" variety.
I view @nogc as a safeguard against crashes when I let threads run while the garbage collector is in a collection phase. A means to bypass "stop-the-world" collection by having pure @nogc threads.
No, this is something completely different, see my answer before.
Got it, I didn't see that answer until after I wrote my reply. Ola.
