Count / Borrow Elision Optimization

[andrew-johnson-4]

Reference Counting can be optimized away if Borrowing and Ownership can be proven to be semantically equivalent.

This optimization creates a happy medium between Ownership languages like Rust which can be annoying to work with vs implied GC languages which can be somewhat slow or unpredictable. Reference Counting becomes a fallback if ownership becomes too complex. At that point the compiler takes on the burden that Rust programmers are faced with writing (and usually compilers do a better job at this sort of closed deterministic tasks).