chromatic wrote:
We'd have to detect when it's safe to recycle a CallContext, but we *could* hijack its destroy(), let the GC capture a few, and then store them in the cache by size and avoid subsequent GC runs.
It reminds me pre-PMC version of Parrot_Contexts... It's really hard to make it correct.
-- Bacek _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
