On Friday, 17 October 2014 at 16:56:50 UTC, Jeremy DeHaan wrote:
I'm curious as to why using scope to allocate classes on the
stack was marked for future deprecation.
It was never implemented correctly (it is supposed prove it never
leaves the scope, and is thus safe to be on the stack), so ra
I'm curious as to why using scope to allocate classes on the
stack was marked for future deprecation.
I mean, sure it could be potentially unsafe, but the new library
solution (using std.typecons.scoped) does the exact same thing
and is just as unsafe for the same reasons, is it not? I would