I'm particularly excited for this too. We're starting to see a lot on the horizon: * Austral is using linear types for zero-cost memory safety [0] and then all

I'm particularly excited for this too. We're starting to see a lot on the horizon: * Austral is using linear types for zero-cost memory safety [0] and then allows for borrowing on top of that. Val does something similar called mutable value semantics, which is pretty interesting [3]. * Vale brings borrow checking up to the regions level [1] which gives borrow checking benefits while still allowing mutable aliasing, which makes it much more flexible and ergonomic. * Cone uses borrow checking on top of any user-specified allocation strategy, such as single ownership, RC, GC, etc. [2] [0] https://borretti.me/article/introducing-austral https://borretti.me/article/introducing-austral [1] https://verdagon.dev/blog/zero-cost-memory-safety-regions-part-1-immutable-borrowing https://verdagon.dev/blog/zero-cost-memory-safety-regions-pa... [2] https://cone.jondgoodwin.com/ https://cone.jondgoodwin.com/ [3] https://github.com/val-lang/val https://github.com/val-lang/val