Even more tangentially: This is one of the reasons I'm having a great time developing a game in Rust. You never want lock contention in a game if at all avoida

Even more tangentially: This is one of the reasons I'm having a great time developing a game in Rust. You never want lock contention in a game if at all avoidable, and in a lot of cases taking a lock is provably unnecessary. For example: Each frame is divided into phases, and mutable access to some shared resource only needs to happen in one specific phase (like the `update()` function before `render()`, or when hot-reloading assets). With scoped threads and Rust's borrowing rules, you can structure things to not even need a mutex, and be completely certain that you will receive a stern compiler error if the code changes in way so you do. When possible, I'd always love to take a compiler error over a spike in the profiler.