#polonius#borrowchecker#non-lexicallifetimes
4.8K subscribers • 4 videos on Hallway
Advanced. Deep dive for people who know the field.
20K views6 years ago4 recommendations
Systems programmingProgramming languagesRustCompilers and interpretersMemory management
Niko Matsakis explains Polonius, a new formulation of the Rust borrow checker that tracks origins instead of lifetimes to accept more safe programs.
Rust 2018 brought with it “non-lexical lifetimes” (NLL), a big overhaul of how the borrow checker worked that allowed it to accept a lot more programs. And yet, we’re still not accepting the full range of programs that was envisioned by the original NLL RFC – this is both for performance reasons and because the formulation didn’t turn out to be as flexible as originally thought. Polonius is a “reframing” of Rust’s borrow checker. It works quite differently than the original system. Rather than tracking how long each reference is used (its “lifetime”), it tracks where each reference may have come from (its “origin”) – and it does so in a very fine-grained way. As a result, Polonius is able to accept all the programs that the NLL RFC envisioned, and a few more! We also believe it can be made more performant (though that has yet to be fully proven out). This talk will explain how Polonius works in a simple and example-driven style. It will help you to gain a deeper understanding of how Rust’s borrow checker works internally. --- Note from the conference: The slides for this talk were not captured and we've re-recorded them after the fact. Some of the visuals did not work perfectly, and for that we apologize.What people say. Recommended as a great explanation of the limitations of non-lexical lifetimes and how the Polonius borrow checker solves them.
u/panstromekin r/rust • Recommends
On “Is the borrow checker wrong here?”
u/hniksicin r/rust • Recommends
On “Polonius revisited, part 1: the next generation of the Rust borrow checker”
u/SeriToolsin r/rust • Recommends
On “What's the status of the Polonius borrow checker?”
u/olemni7in r/rust • Recommends
On “Confusion around borrow checker analysis of loops”
u/minauteurin r/rust • Mentions
On “Is the borrow checker wrong here?”
u/CodenameLambdain r/rust • Mentions
On “Is the borrow checker wrong here?”
u/phazer99in r/rust • Mentions
On “What cons of rust should I know before I begin?”
u/hniksicin r/rust • Mentions
On “Food for thought: Simple Rust a'la Simple Haskell?”
u/hniksicin r/rust • Mentions
On “Self-referential types for fun and profit”
u/ArtisticHamsterin r/rust • Mentions
On “How to make this code compile?”
u/SirKastic23in r/rust • Mentions
On “Hey Rustaceans! Got a question? Ask here (15/2023)!”