A Grounded Conceptual Model for Ownership Types in Rust
summary
Created an Ownership Inventory to measure Rust misconceptions and finds learners predict compiler errors 64% of the time but produce valid counterexamples only 31% and justifications 15%. Designs a permissions model that visualizes flow‑sensitive read/write/own permissions, implements a compiler plugin using a MIR interpreter to run non‑compiling programs and generate state and borrow‑checker visualizations, rewrites the ownership chapter of The Rust Programming Language, and runs an A/B test with 342 completions that shows a 9% improvement (d=0.56) overall and gains on 10/18 questions.
AI-written summary · about
chapters (11)
- 0:00Ownership types in Rust
- 1:04Learning Rust ownership challenges
- 2:31Testing ownership misconceptions
- 4:37Syntactic vs semantic understanding
- 6:02Conceptual model design
- 7:30Dynamic semantics visualization
- 8:51Static semantics and permissions
- 12:00Rewriting Rust’s ownership
- 12:42Pedagogy evaluation with A/B
- 14:30Key takeaways
- 15:56Q&A
related talks
56mVisualizing and Explaining Rust's Ownership Model
16mPlace Capability Graphs: A General-Purpose Model of Rust’s Ownership and Borrowing(…)
28mYou Don't Own Me
40mAdvanced Rust Programming Techniques
40mAgainst Borrowing: Own the forest, not the trees!
59mRust for C++ developers - What you need to know to get rolling with crates
27mParadigms of Rust for the Go Developer
45mRust: safe and concurrent. But how does it do it?