credit where credit is due

[web.git] / ralf / _posts / 2022-08-08-minirust.md

diff --git a/ralf/_posts/2022-08-08-minirust.md b/ralf/_posts/2022-08-08-minirust.md
index f13285b26a5c8fd63a377a1180c97f64e390a8bf..821c3b97130ab96c8fca895346092954ae18812f 100644 (file)
--- a/ralf/_posts/2022-08-08-minirust.md
+++ b/ralf/_posts/2022-08-08-minirust.md
@@ -48,7 +48,9 @@ On the other hand, there are many things that it *can* explain in full precision
 - what happens when *casting* between pointers and integers
 - padding (that's why tuples can have 2 elements, so there can be padding between them)
 
-If you re not used to reading interpreter source code, then I guess this can be rather jarring, and there is certainly a *lot* of work that could and should be done to make this more accessible.
-But just being able to talk about these questions with precision *at all* has already lead to some interesting discussions in the UCG WG (some of which made me change my mind, and change MiniRust accordingly), so for now it is serving its purpose, and maybe some of you can find it useful, too.
-And hopefully we can use it as a starting place for seriously tackling the issue of an *official* specification of Rust.
+If you are not used to reading interpreter source code, then I guess this can be rather jarring, and there is certainly a *lot* of work that could and should be done to make this more accessible.
+(Like, examples. I hear people like examples.)
+But just being able to talk about these questions with precision *at all* has already lead to some interesting discussions in the UCG WG, some of which made me change my mind -- thanks in particular to @digama0 and @JakobDegen for engaging deeply with my ideas.
+So for now it is serving its purpose, and maybe some of you can find it useful, too.
+Hopefully we can even use this as a starting place for seriously tackling the issue of an *official* specification of Rust.
 More on that soon. :)