Compile-Time Evaluation, Interpreted Rust, and UB Sanitizing: Talking to Oliver Scherer about Miri Dec. 23, 2019

from Rustacean Station·

In the first of our mini-interviews from RustFest 2019, we talk to Oliver Scherer about Miri, an interpreter for rustc’s internal bytecode, its use in const-evaluation, and its potential as an external tool for sanitizing unsafe code.



In the first of our mini-interviews from RustFest 2019, we talk to Oliver Scherer about Miri, an interpreter for rustc’s internal bytecode, its use in const-evaluation, and its potential as an external tool for sanitizing unsafe code. Contributing to Rustacean Station Rustacean Station is a community project; get in touch with us if you’d like to be interviewed, propose a topic for an episode, or help create the podcast itself! Twitter: @rustaceanfm Discord: Rustacean Station Github: @rustacean-station Email: hello@rustacean- station.org Timestamps & referenced resources [@01:15] - What is const- evaluation and what can you do with it? [@03:23] - What is Miri and how long has it been in development? [@07:05] - What does the future hold for Miri? [@07:54] - How long have you been working on rustc and Miri? [@12:22] - How much of Miri does rustc use today? [@13:33] - How does Miri help people detect undefined behavior in unsafe code? [@16:46] - How would a user begin using Miri directly to test their unsafe code? [@19:15] - What happens if you try to const-evaluate unsafe code? [@20:33] - What’s next for const-evaluation in rustc? [@21:58] - Who else is helping to develop Miri? Credits Intro Theme: Aerocity Audio Editing: alphastrata Hosting Infrastructure: Jon Gjengset Show Notes: Ben Striegel Hosts: Ben Striegel