On 04/04/2018 09:18 AM, 12345swordy wrote:
On Wednesday, 4 April 2018 at 04:49:10 UTC, Andrei Alexandrescu wrote:
I'm working on a simple older idea to get it out of the way in preparation for the more difficult DIPs to come:


This is not officially reviewable yet, but conveys the gist and could use some early feedback. Any insight will be appreciated.



No attempts to make class deallocation @nogc attribute friendly? This is a major PIA for me. The current attempts at this involve various workarounds (See automem library for example), which even then does not solve all the problems it currently have.

Can you please give more detail on that? You mean the destructor of Object is automatically generated with a bad signature?

Reply via email to