Memory management design

[John Colvin]

On Wednesday, 10 July 2013 at 13:00:53 UTC, Kagamin wrote:
> On Wednesday, 10 July 2013 at 08:00:55 UTC, Manu wrote:
>> most functions may actually be @nogc
>
> Most functions can't be @nogc because they throw exceptions.

I think I mentioned before, elsewhere, that @nogc could allow 
exceptions. No one who is sensitive to memory usage is going to 
use exceptions for anything other than exceptional circumstances, 
which perhaps don't need the same stringent memory control and 
high performance as the normal code path.


How much of the exception model would have to change in order to 
free them from the GC? I don't see high performance as a concern 
for exceptions so even an inefficient situation would be fine.