Is there a way to make sure (by inspection or enforced by the compiler) that the moved ref RC == 1, other then wrapping the ref in an `isolated[]`? When the ref counter of the moved object > 1, both threads will have a reference to the same object, leading to disaster.
`isolated[]` is not practical to work with, as the object needs to be wrapped in an isolated[] at construction time, which makes it cumbersome to work with the encapsulated value.
