D Language 2.0

[Andrei Alexandrescu]

BCS wrote:
> Hello Andrei,
> 
>> It's reasonable to say that you decide at application design level
>> what memory management approach you want to choose. That doesn't
>> fragment the community. The decision is similar to many others made at
>> the same level: libraries used, build flags, target platform(s),
>> pointer size (32 vs. 64, not an option yet for dmd), etc.
>>
> 
> IIRC you can right now point to code that makes the memory management 
> choice at a much finer level: lots of graphics and other types of RT 
> code have large chunks of code that do zero allocation (they don't even 
> uses malloc) but rather keep externally supplied buffers around to work 
> with.

Nonono. That's not a memory management choice. It's a choice to avoid 
any memory management altogether.

> In D where detecting allocations is harder than just greping for 
> malloc, having compiler support would be really nice.

I don't think the language needs to cater to all special needs. Tomorrow 
someone comes and says they don't want to deal with unsigned integers. 
Oh wait...


Andrei