Note that the comment in John's abstract example is wrong: ;; Alternative: (for-each free-resource ;; (unregister-guardian handle-guardian))
This misinterprets what unregister-guardian does; it returns the accessible, not the inaccessible objects. Am Do., 12. Sept. 2024 um 13:03 Uhr schrieb Marc Nieper-Wißkirchen < [email protected]>: > I may remove the guardian-unregister procedure from the specification as > it is not deterministic. > > Comments? > > Can you think of use cases that wouldn't work without guardian-unregister? > > Marc >
