Should noncopyable types release system resources in `deinit`?

Hi all, In the swift-system pitch for a noncopyable Win32.FileHandle, we keep coming back to one question: should a noncopyable type release a system resource, like a file handle, in its deinit? This has come up repeatedly, so as @FranzBusch suggested, I'd like to ask for community perspectives and guidance from the LSG. The answer is important for more than just this type. swift-system already ships Mach.Port and IORing, which release their resources in deinit, and noncopyable owners for Wind...