Would it be feasible, when gc.disable() is issued, to unlock the heap? Clearly it would need to be re-locked when gc.enable() was issued and for the duration of gc.collect(). The purpose would be to enable a user to write interrupt callbacks which used the heap. It would be their responsibility to disable the relevant interrupts before issuing gc.collect() or gc.enable().

Envisaged use case: developers of control systems wishing to run the principal control loop as a timer callback for a well-defined update rate. Many filtering algorithms depend on floating point operations.