If I understand the article correctly (and I'm not a Rust programmer), the above is an optimization that permits the programmer to write code that is correct wi

If I understand the article correctly (and I'm not a Rust programmer), the above is an optimization that permits the programmer to write code that is correct with regard to object lifetimes, but currently rejected by the compiler. This is because the current borrowing model is too simple to account for that particular case, and hence, a new model is being developed that makes compiling this code possible without sacrificing correctness. But, still, the whole selling point of Rust is "flow-sensitive analysis (...) for a language feature that affects whether code is accepted or rejected". Accepting or rejecting some code based on whether it fits the memory model of that language is the main advantage that Rust has over other strongly typed statically compiled languages.