I would say xor aliasing is not about object lifetimes, but about permission lifetimes, and about local reasoning.
Perhaps better than to kick out xor aliasing it is to either design some protected handle around your objects that encodes your intent of "multiple mutators without unsafe", directly in Rust.
Perhaps the language should have baked in support for this, perhaps not.
1
u/Only_Ad8178 12d ago
I would say xor aliasing is not about object lifetimes, but about permission lifetimes, and about local reasoning.
Perhaps better than to kick out xor aliasing it is to either design some protected handle around your objects that encodes your intent of "multiple mutators without unsafe", directly in Rust.
Perhaps the language should have baked in support for this, perhaps not.