I sort of like the idea of folks relying on Fil-C features and then sticking with it. :-) Right now, the Fil-C runtime already relies on the GC in that it crea

I sort of like the idea of folks relying on Fil-C features and then sticking with it. :-) Right now, the Fil-C runtime already relies on the GC in that it creates objects that don’t get freed. So it would already be hard to provide diagnostics about leaked objects. And since the GC is concurrent and runs at unpredictable times, any diagnostics it reported would be flaky. FUGC really is designed to be something you rely on in production as opposed to being a leak detector.