Deprecation Policy and new GC
Jonathan "Duke" Leto
jonathan at leto.net
Tue Feb 15 04:16:55 UTC 2011
Howdy,
> I'd propose this compromise: We merge the new gc in after mikehh cuts 3.1
> but make gc_ms2 the configure-time default for 3.2 and 3.3, unless an option
> specifying otherwise is passed to Configure.pl. This would let users who
> aren't expecting the write barrier changes continue to use Parrot as-is, but
> would also let Rakudo take advantage of the speed improvements from the
> generational gc. The default for non-release builds would be the
> generational gc, since that's what will need the most testing and developer
> tuits.
+1
Duke
--
Jonathan "Duke" Leto
jonathan at leto.net
http://leto.net
More information about the parrot-dev
mailing list