On Friday, 24 May 2013 at 08:01:35 UTC, Jacob Carlborg wrote:
On 2013-05-24 01:51, Joseph Rushton Wakeling wrote:
This also seems to suggest that an ideal solution might be to
have several
different GC strategies, the choice of which could be made at
compile time
depending on what's most suitable for the application in
question.
You can already swap the GC implementation at link time.
Yep, exactly. Hard-wired GC is not the problem. Lack of
alternative GC's is the problem. Lack of tools to reliably
control avoiding of GC calls at all is the problem.
