From 30ed45a87c23ef255c4e46877f4180d158146f32 Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Mon, 28 Sep 2020 19:00:40 +0200 Subject: [PATCH] show a bit elss text on the index --- personal/_posts/2020-09-28-miri.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/personal/_posts/2020-09-28-miri.md b/personal/_posts/2020-09-28-miri.md index e0529ad..8dc5e4c 100644 --- a/personal/_posts/2020-09-28-miri.md +++ b/personal/_posts/2020-09-28-miri.md @@ -11,11 +11,11 @@ You can think of it a as very thorough (and very slow) version of valgrind: Miri As such, it is most helpful when writing unsafe code, as it aids in ensuring that you follow all the rules required for unsafe code to be correct and safe. Miri also detects memory leaks, i.e., it informs you at the end of program execution if there is any memory that was not deallocated properly. + + However, being an interpreter, Miri is limited in the kinds of code it can execute -- everything that would usually involve interacting with C libraries or the operating system needs to be specifically supported, as C code cannot be interpreted by Miri. Miri also lacks support for some Rust features that are hard to interpret, but we are slowly closing these gaps. - - ## Recent and past progress in Miri During the last 1.5 years, thanks to a series of excellent contributors, we made a lot of progress towards supporting more and more Rust code to run in Miri. -- 2.30.2