update my afiliation

[web.git] / personal / _posts / 2020-09-28-miri.md

diff --git a/personal/_posts/2020-09-28-miri.md b/personal/_posts/2020-09-28-miri.md
index e0529ad43f39dbd7b534933f3396764cbd783841..62f3759ebbe39dd5f9fee676950f671d7e30a4e2 100644 (file)
--- a/personal/_posts/2020-09-28-miri.md
+++ b/personal/_posts/2020-09-28-miri.md
@@ -1,6 +1,7 @@
 ---
 title: "What (not so) recently happened in Miri"
 categories: rust
+reddit: /rust/comments/j1fxd3/what_not_so_recently_happened_in_miri/
 ---
 
 A lot has happened in Miri over the last year and a half, and I figured it would be a good idea to advertise all this progress a bit more widely, so here we go.
@@ -11,11 +12,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.
 
+<!-- MORE -->
+
 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.
 
-<!-- MORE -->
-
 ## 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.