On Saturday, 17 June 2017 at 13:05:50 UTC, Adam D. Ruppe wrote:
This is why I consider @nogc to be an *extremely* niche feature
and generally harmful. It makes things look a lot harder than
it really is - people confuse `@nogc` with "no gc". Instead, I
suggest just minding the list and using runtime profiling and
debugging to ensure your needs are met in actual practice.
As a counterpoint: It's true that it's a bit niche, but when you
have "no gc" then @nogc really helps with peace of mind (only one
allocation and you may crash).