Interrupt unsafety of WITH-OPEN-STREAM and -FILE

[Tobias C. Rittweiler]

Neither WITH-OPEN-STREAM, nor WITH-OPEN-FILE disable
interrupts to prevent leakage due to interrupts.

Anything against doing that?

A further idea:

Is it possible to determine whether an FD was reclaimed, or not?

If the answer to that question happens to be yes, how about a
finalizer on FD-STREAMs which emits a warning in case an
FD-STREAM is garbage-collected that is not reclaimed yet?

[Tobias C. Rittweiler (tcr)]

I forgot to mention that despite of using W/O-INTERRUPTS
around the UWP in WITH-OPEN-FILE, one could still lose
an FD within OPEN itself. And disabling interrupts during
the extent of OPEN does not sound very right either in case
of blocking.

Still, disabling interrupts around the UWP would minimize the
window.

[Nikodemus Siivola (nikodemus)]

As long as arbitrary user-code isn't being run with interrupts silently disabled and the performance cost isn't terrible, I'm all for increasing interrupt safety.