This is a very good talk showing how relying only on the borrow-checker will not be enough when designing systems. The context of the video is multiplayer games and memory management, but there is a great lesson to learn here: Sometimes we will seem to have solved issues by implicitly silencing the borrow-checker and not really dealing with problems. Rust compiler will cry out when there is a problem, but it is the responsibility of the programmer to go further than fixing the symptoms.