On Tuesday, 11 September 2012 at 10:28:29 UTC, bearophile wrote:
SomeDude:
It's a bad solution imho. Monitoring the druntime and hunting
every part that allocates until our codebase is correct like
Benjamen Thaut is a much better solution
Why do you think such hunt is better than letting the compiler
tell you what parts of your program have the side effects you
want to avoid?
The compiler option warning about undesirable heap allocations
will allow for complete undesirable allocations to be identified
much more easily and without missing anything. This is a general
solution to a general problem where a programmer wishes to avoid
heap allocations for whatever reason.
--rt
