On Tuesday, 26 August 2014 at 11:47:39 UTC, Manu via
Digitalmars-d wrote:
This is the initiative I've been dreaming of for years!
I'll give it a critical review when I have some time. But in
the mean time
at first glance, I just wanted to say, very nice work! :)
I had a suspicion you would like it ;-)
This is largely inline with my thoughts since I first came to
D, except you
flesh out a few problem areas (return scope, which we discussed
at length
at dconf2013), and the ideas appear to be quite sound.
I've heard that mentioned a few times. I guess it was an informal
discussion only, not an official talk, right? I only know about a
few discussions afterwards on the news group.
This direction really opens up the language to support manual
and
user-defined memory management at a much deeper and more useful
level.
In my experience, manual/custom memory management depends
extensively on
templates, and also implies that practically every api in any
library
anywhere must also receive template args, such that it can
receive objects
templated with custom allocation strategies.
D is a language that is acutely susceptible to
over-templatisation and
extreme template bloat. This work on scope is critically
important to
mitigate that tendency of D in library code.
I'm looking forward to hear your thoughts about it, because
you're one of the people who are involved in large complex
projects where this is relevant. For me, it is until now only a
theoretical exercise, it's important to hear from someone who can
assess how it would work out in practice.
I'm also curious about Walter and Andrei's opinion (I believe
they are quite busy with other things at the moment, so we'll
have to wait), and Kenji and others who can give an estimate
about the implementation.
