I have no plans myself, but I think many applications would benefit from incremental collection. I also think that implementing an incremental GC for Racket is within reach --- as much as for any runtime system.
That is, unlike so many other things in our infrastructure, the GC is not so tangled with everything else that it would be difficult to change by itself. Granted, GC implementation can be fairly challenging on its own. At Sat, 04 Jul 2015 17:26:00 -0400, Neil Van Dyke wrote: > Any plans for new interesting GC/memory features in Racket? > > For example, being able to inhibit GC for a time, being able to adjust > the GC trigger parameters dynamically, different ways to minimize GC > pauses or slowdown in the app behavior, real-time constraints on GC, > special support to help programmers avoid/reduce garbage generation, etc.? > > Neil V. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
