> Except of course that the only way to do this is by calling the function > unsafeIsolate(), which is unsafe.
We're running in circles now. And you didn't answer my questions either. If your data is not isolated no amount of type system voodoo that can prove isolation is gonna change anything. Why spend the complexity budget on expressive and compiletime safe isolation when isolation itself might be too cumbersome to work with anyway?
