Andrei Alexandrescu Wrote: > And how would you use such a feature effectively? I've seen such > "optional implementation" policies in standards such as SQL > (compatibility levels) and C++ (export). They _always_ fare disastrously.
Just like we do it now: write code for the garbage collected environment of your choise. > It's not about difficulty as much as constraining GC implementers > unnecessarily. Again: use a heap tuned for manual management to manage > memory manually, and a heap tuned for automatic management to manage > memory automatically. I think it's a very reasonable stance. Yes, heap is used by language expressions new and delete. That's exactly what want to say: whether deallocation is supported or not is a feature of chosen runtime and programming style.
