Vale's first prototype for immutable region borrowing
I keep wondering what "safe" means in the context of generational references.If I understand clearly, this prevents use-after-free and double-free? Thus, the program can still fail on a memory access when the expected and actual generations don't match? In this regard, this seems less "safe" than reference counting, tracing garbage collector, or borrow checking?