https://issues.dlang.org/show_bug.cgi?id=8293

--- Comment #3 from Vladimir Panteleev <dlang-bugzilla@thecybershadow.net> ---
(In reply to Marco Leise from comment #2)
> Which more or less means that if such an object is allocated with new, there
> must always be a pointer to it to prevent automatic collection. Because it
> has to be manually destroyed to be safe.
> Or can the GC be improved in this regard?

Just use C malloc. This is what RefCounted!T does.

--

https://issues.dlang.org/show_bug.cgi?id=8293

RazvanN <razvan.nitu1305@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |razvan.nitu1305@gmail.com
         Resolution|---                         |MOVED

--- Comment #4 from RazvanN <razvan.nitu1305@gmail.com> ---
This should be the job of a third party tool. It's not the compiler's job to check for things like this.

--