On Sunday, 20 July 2014 at 08:29:55 UTC, Jonathan M Davis wrote:
What you will probably need to do is to not try and use the
same type as both shared and non-shared if it has a destructor.
Unfortunately this option would require an unrealistic lot of
refactoring for me. I'm basically using thi
On Sunday, 20 July 2014 at 02:57:44 UTC, Vlad Levenfeld wrote:
I have a Resource struct that is supposed to free some memory
when it gets destroyed. Unfortunately, I can't define a
destructor. If I do, the compiler complains that it can't
destroy the shared versions. If I define a shared destru
I have a Resource struct that is supposed to free some memory
when it gets destroyed. Unfortunately, I can't define a
destructor. If I do, the compiler complains that it can't destroy
the shared versions. If I define a shared destructor, the
compiler complains that it can't disambiguate between
