There are some design decisions mean Rust can't work with generational references and regions, unfortunately. They're incompatible with their form of borrow che

There are some design decisions mean Rust can't work with generational references and regions, unfortunately. They're incompatible with their form of borrow checking. In Vale, each struct has a generation in theory, but they are often merged with their parent struct. It requires some pretty interesting logic which can't be implemented in Rust. Regions require truly immutable references, which Rust doesn't have. Their shared references are unfortunately foiled by the RefCell escape hatch. Additionally, the rest of Vale's future design prioritizes developer productivity more than Rust has, in my opinion: - A coroutine-like mechanism instead of Rust's async/await function coloring, and structured concurrency which doesn't involve the Sync/Send "data coloring" problem. - Vale's borrowing is done on the region level and on an opt-in basis, so users can decide to only use borrow checking where it makes sense. - Linear typing ("Higher RAII") which allows for different static checks which aren't quite as infectious as aliasability-xor-mutability. I love Rust, but it has some quirks that make it much more suited to low-level development than these higher user cases. I don't see how Rust can fix them, but there are some smart people working on it and I hope they figure out a way, because the world needs a fast and safe language that's easy to learn and focuses on productivity, even if it's not Vale ;)