On Tuesday, 8 October 2013 at 15:43:46 UTC, ponce wrote:
Is there a plan to have a standard counter-attack to that kind of overblown problems?It could be just a solid blog post or a @nogc feature.
It is not overblown. It is simply "@nogc" which is lacking but absolutely mandatory. Amount of hidden language allocations makes manually cleaning code of those via runtime asserts completely unreasonable for real project.
