rust-lang

miri

Rust2016–2026

rust-lang / miri

miri

An interpreter for Rust's mid-level intermediate representation

Languages & Compilers

Explore on GitHub Read Hacker News discussions

33Distinct people

41Mentions

1Explicit recommenders

6.7KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

An interpreter for Rust's mid-level intermediate representation

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

If you have a codebase that uses unsafe, I highly recommend running your tests through Miri (cargo miri nextest) and seeing what spills out. I ran tests for a codebase at work…

landr0id used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:01:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year41 dated mentions

Observed mentions: 2016-03-04 11:38:42 UTC to 2026-09-17 14:02:35 UTC.

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	7	0	7
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	4	0	4
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	2	0	2
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	2	1	1
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	2	0	2
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	3	0	3
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	4	0	4
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	1	0	1
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	5	0	5
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	6	1	5
2026 (partial)	2026-01-01 00:00:00 UTC	2027-01-01 00:00:00 UTC	5	0	5

What Hacker News says

7 sources

kibwen·Dec 2, 2016

Which makes me wonder if Miri ( https://github.com/solson/miri ) counts as an alternate implementation of the frontend. Combined with, say, Cretonne ( https://internals.rust-lang.org/t/possible-alternative-compi... ) I wonder if we couldn't cobble together an alternate frankencompiler for mitigating RoTT.

In Reflections on Rusting Trust

tatterdemalion·Oct 22, 2016

The project you're thinking of is called miri, I don't really know the state of it either. https://github.com/solson/miri

In 2017 Rust Roadmap

eddyb·Apr 27, 2016

You are correct that a Rust interpreter would work great on MIR, which is why Scott Olson (@tsion) has been working on one: https://github.com/tsion/miri (check out the slides and the report).

In Introducing MIR

steveklabnik·Apr 27, 2016

Yes, in theory, you could write a new backend that uses MIR. Miri, linked at the end of the post[1], is an example: it interprets MIR, rather than using LLVM to generate machine code. 1: https://github.com/tsion/miri

In Introducing MIR

kibwen·Apr 27, 2016

Speaking of comparisons to bytecode, there's currently a student writing a MIR interpreter as part of their research: https://github.com/tsion/miri . There are some that foresee this being added to the Rust compiler itself, to enable more extensive compile-time constant evaluation.

In Introducing MIR

steveklabnik·Apr 27, 2016

Inside rustc, MIR is a data structure. The outputs you see here are a human-readable export of that, the compiler does not emit text and then re-parse. Projects in Rust, like miri, hook directly into the compiler and use the datastructures as well, they don't parse the output you see here: https://github.com/tsion/miri/blob/master/src/bin/miri.rs (The post has been amended to try to clear this up a bit)

In Introducing MIR

eddyb·Mar 4, 2016

Yes, there are no immediate plans for anything other than MIR at the imperative-semantic level (the compiler also uses HIR, which is mostly a desugared AST and not related to LLVM IR). Currently, initial support for lowering MIR to LLVM IR is close to complete and it might be enabled in the next beta (or the one after that). None of the analysis passes have started their transition to MIR, though (there is a well-typed check to catch bugs in MIR generation, but that's about it). There's also talk of using MIR for compile-time (pure) function evaluation [1] and some out-of-tree experimentation with interpreting it [2]. [1] https://internals.rust-lang.org/t/mir-constant-evaluation/31... [2] https://github.com/tsion/miri

In No Compiler – On LLVM, and writing software without a compiler