Any ideas on how one can simplify the borrow checker?
Eventually as optimization point, for the few use cases where the ultimate performance is needed, provide a subset of borrow checker capabilities.
Examples of current efforts into this direction, D, Swift, Haskell, Chapel, some .NET ongoing research.
Reframing the system in this way will (hopefully) make things be flexible enough to Just Work™ without surprises, while providing the same guarantees as the current borrow checker. The video itself has a motivating example or two that shows where this stuff would be helpful.