manual memory management

[Jonathan M Davis]

On Monday, January 07, 2013 23:26:02 Rob T wrote:
> Is this a hard fact, or can there be a way to make it work? For
> example what about the custom allocator idea?
> 
> From a marketing POV, if the language can be made 100% free of
> the GC it would at least not be a deterrent to those who cannot
> accept having to use one. From a technical POV, there are
> definitely many situations where not using a GC is desirable.

It's a hard fact. Some features (e.g. appending to an array) require the GC 
and will always require the GC. There may be features which currently require 
the GC but shouldn't necessarily require it (e.g. AAs may fall in that camp), 
but some features absolutely require it, and there's no way around that. You 
can limit your use of the GC or outright not use it at all, but it comes with 
the cost of not being able to use certain features (mostly with regards to 
arrays).

- Jonathan M Davis