April 15, 2014
https://issues.dlang.org/show_bug.cgi?id=5219

--- Comment #15 from bearophile_hugs@eml.cc ---
See the start of the development of @nogc here:

https://github.com/D-Programming-Language/dmd/pull/3455

--
April 16, 2014
https://issues.dlang.org/show_bug.cgi?id=5219

bearophile_hugs@eml.cc changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #16 from bearophile_hugs@eml.cc ---
This issue has 11 votes, but after this comment by Ola Fosheim G.:

> Btw, I think you should add @noalloc also which prevents both new and malloc. It would be useful for real time callbacks, interrupt handlers etc.

Walter has started a sub-thread answering:

> Not practical. malloc() is only one way of allocating memory - user defined custom allocators are commonplace.

So I presume @noheap has very little hope, and currently the best chance to have something similar is @nogc. So unless you want to rename this issue "@nogc annotation", I think it should be closed down.

--