I think std.typecons.Unique should place the object ownership under the control. Unique!T holds the unique ownership of given object typed T. yes, Unique can hold an object on heap, but also should be able to hold stack allocated object. (In this case, Unique!T will work as rebindable scoped!T, IMO)
An experimental implementation of mine. https://github.com/9rnsr/scrap/blob/master/typecons/unique.d Kenji Hara 2012/2/10 Martin Nowak <[email protected]>: > I'll take a shot at implementing std.typecons.Unique. > Any opinions or ideas? > > My main goals is that it should use malloc under the covers. > _______________________________________________ > phobos mailing list > [email protected] > http://lists.puremagic.com/mailman/listinfo/phobos _______________________________________________ phobos mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/phobos
