Safely Adding a Moving Garbage Collector to a Non Garbage Collected Language
Retro-fitting precise Garbage Collection (GC) to an existing language is hard and thus conservative GC is genearlly used instead. However, conservative GC is slower, and can cause memory leaks. Correctly identifying all pointers to an object makes retro-fitting a precise, moving collector particularly difficult. This paper outlines my proposed solution to add an optional, precise, moving GC to Rust with an intuitive API. It lets programmers choose which Rust objects are GC’d, with references to and from other non-GC’d objects also possible.
Tue 6 Nov Times are displayed in time zone: Guadalajara, Mexico City, Monterrey change
13:30 - 15:00
|Efficient Static Analyses to Identify Opportunities for Replacing Type Code with Subclass and State|
Jyothi VeduradaIIT Madras
|Safely Adding a Moving Garbage Collector to a Non Garbage Collected Language|
Jacob HughesKing's College London