From 1014facc01a7f23163450af7c1dd57bbd09ce543 Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Tue, 24 Jul 2018 17:03:13 +0200 Subject: [PATCH 1/1] add thanks --- personal/_posts/2018-07-24-pointers-and-bytes.md | 1 + 1 file changed, 1 insertion(+) diff --git a/personal/_posts/2018-07-24-pointers-and-bytes.md b/personal/_posts/2018-07-24-pointers-and-bytes.md index a51fb48..8338de4 100644 --- a/personal/_posts/2018-07-24-pointers-and-bytes.md +++ b/personal/_posts/2018-07-24-pointers-and-bytes.md @@ -203,6 +203,7 @@ Using `Uninit` instead of an arbitrary bit pattern means miri can, in a single e We have seen that pointers can be different even when they point to the same address, and that a byte is more than just a number in `0..256`.[^4] With this, I think we are ready to look at a first draft of my "2018 memory model" (working title ;) -- in the next post. :) +Thanks to @rkruppe and @nagisa for help in finding arguments for why `Uninit` is needed. If you have any questions, feel free to [ask in the forums](https://internals.rust-lang.org/t/pointers-are-complicated-or-whats-in-a-byte/8045)! [^4]: And just to be clear, I am talking about a pointer or byte in the model of an optimized *programming language* here. When modeling hardware, everything is different. -- 2.30.2