On Monday, 10 November 2014 at 20:00:51 UTC, Walter Bright wrote:
I'm not at all sure that how a type is allocated should be part of the type itself. There are an infinite way things can be allocated.
Nitpick: it's about memory _management_, not _allocation_.But the DIP is also underspecified. E.g., is it allowed to embed a @nogc type in a class? If not, what if that class again is wrapped in std.typecons.Scoped?
