The Usability of Ownership
This addresses usability issues for Rust programmers, particularly newcomers, but is incremental as it builds on existing knowledge without introducing new methods.
The paper tackles the challenge of interpreting and responding to ownership errors in Rust's borrow checker, a notorious learning barrier, by exploring user difficulties and suggesting educational and automated interventions to improve usability.
Ownership is the concept of tracking aliases and mutations to data, useful for both memory safety and system design. The Rust programming language implements ownership via the borrow checker, a static analyzer that extends the core type system. The borrow checker is a notorious learning barrier for new Rust users. In this paper, I focus on the gap between understanding ownership in theory versus its implementation in the borrow checker. As a sound and incomplete analysis, compiler errors may arise from either ownership-unsound behavior or limitations of the analyzer. Understanding this distinction is essential for fixing ownership errors. But how are users actually supposed to make the correct inference? Drawing on my experience with using and teaching Rust, I explore the many challenges in interpreting and responding to ownership errors. I also suggest educational and automated interventions that could improve the usability of ownership.