Chapter on MIRI?

[mark-i-m]

... perhaps as a subchapter under the MIR chapter?

[Michael-F-Bryan]

Weren't there plans to use miri to help with compile time function execution (constexpr)? If so, knowing how it works and how to use it may be useful.

[mark-i-m]

@Michael-F-Bryan see rust-lang/rust#46882 which is actually very close 🎉

[oli-obk]

Feel free to assign this to me (so I'll find it again :D). I'll write up something.

What level of detail did you have in mind?

[mark-i-m]

@oli-obk Thanks! It doesn't look like I can actually assign you in the issue tracker, unfortunately.

I really don't know much about MIRI, but I guess this is what I was thinking:

• What is it? What is its role in compilation/const evaluation?
• Where does it fit into the compiler pipeline?
• What are the important algorithms? How does it work? Where in the codebase are they defined? (We are looking for things that won't change often, rather than details).
• Perhaps an example would be good?

In general, the goal is that after reading the chapter, somebody wanting to implement a feature that changes MIRI should be able to comfortably read the existing code and have a general idea of what needs to be modified.

[alexreg]

I was just going to file this issue and nominate @eddyb to write it (who mentored me through the bits I contributed to the above PR), but it seems you've beat me too it, so yay!

[eddyb]

@mark-i-m I think the important part about miri isn't the algorithms (which I can't think of any of note), but the data structures, and more specifically how miri represents values and memory allocations.

Everything else is just "match on MIR and apply each instruction to values in local variables and/or memory allocations they might point to" in a way that we could even formally describe as big/small-step semantics on MIR.

[alexreg]

@eddyb You can probably adapt a good deal of material from the original author's report/presentation then. :-)

[mark-i-m]

See #45