MIR
Generated by scripts/gen-format-pages.py from docs/data/format-metadata/, FILE_FORMATS.csv and docs/formats-master.csv. Do not edit by hand: change the source, then run the script.
Rust MIR Preview.
At a glance
| Purpose | A text dump of Rust's mid-level intermediate representation (MIR), as written by rustc's MIR emit and dump options. |
| Extensions | .mir |
| Poka parser | poka-rust-mir |
| Viewer | poka-metadata-card-viewer |
| Depth tier | Metadata card (see Depth tiers) |
| Breadth tier | B4 Summary (see Breadth tiers) |
How much Poka reads
B4 Summary. The container and metadata are read and summarised (counts, properties, structure), but the main content is not rendered.
Confidence: medium (the reviewer read the code). Basis: Reviewed 2026-10-26: read parsers/poka-rust-mir/src/main.rs (179 lines) and plugin.json in full. The crate has no unit tests and no tests/samples.rs, and the corpus has no .mir sample, so the tier rests on reading the code. Covers .mir. The output is a metadata card of counts found by matching text line by line: MIR banners, fn declarations, basic blocks, cleanup blocks, scopes, the highest local index, control flow, calls, drops and asserts, StorageLive and StorageDead, aggregates and casts. Judgement: B4, because the structure is summarised but the source itself is never shown.
What Poka does not read
- The source text is not shown: the card carries only counts and a few sample names, with no code view or highlighting
- Constructs are found by matching text line by line, not by parsing, so multi-line declarations, nested or indented definitions and keywords inside strings or comments can be miscounted
- Files over 64 MiB are cut to the first 64 MiB (the card says so)
- Text that is not UTF-8 is decoded with replacement characters; no other encoding is tried
- Which function each block belongs to is not shown; counts are for the whole file
Sources
- parsers/poka-rust-mir/src/main.rs
- parsers/poka-rust-mir/plugin.json