Oxidize: A Step-Debugger for Static Semantics
summary
A static step-debugger for Rust-like ownership semantics that actually simulates the borrow checker by stepping three explicit contexts: a type context, a memory map, and a borrow-layout mapping addresses to borrow-state unions. Builds a mini-language called Oxidize (no copyable types, no functions or loops yet) and shows concrete rules for moving, borrowing and dropping values, including an offset tuple memory layout to separate tuple and element identities. Prototype handles branch unification and works on example snippets; UI and nonlexical lifetimes remain future work.
AI-written summary · about
chapters (8)
- 0:00Oxidize introduction
- 1:30Pedagogical Rust tools needed
- 3:15Oxidize addresses Rust challenges
- 5:23Step debugging borrow checking
- 7:55Oxidize language design
- 10:06Conditional expressions demo
- 12:53Oxidize future work
- 14:58Q&A
related talks
20mAn Interactive Debugger for Rust Trait Errors
56mVisualizing and Explaining Rust's Ownership Model
06m“RustRover in 2025: Code • Debug • AI”
25m"Compiler-Driven Development: Making Rust Work for You"
25mAre we *actually* IDE yet? A look on the Rust IDE Story
01h 42mIntroduction to Rust (for people who have never used a compiler)
46mSix steps from zero to IDE
01h 06mOn-The-Fly Verification via Incremental, Interactive Abstract Interpretation wi...