This summer, I am again [working on Rust full-time]({{ site.baseurl }}{% post_url 2018-07-11-research-assistant %}), and again I will work (amongst other things) on a "memory model" for Rust/MIR.
---
This summer, I am again [working on Rust full-time]({{ site.baseurl }}{% post_url 2018-07-11-research-assistant %}), and again I will work (amongst other things) on a "memory model" for Rust/MIR.
@@ -201,7+202,8 @@ 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. :)
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. :)
-<!-- If you have any questions, feel free to [ask in the forums]! -->
+
+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.
[^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.