From a86b79df0aaf9d8870ff671e79c0073730cc0adc Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Mon, 14 Dec 2020 17:35:07 +0100 Subject: [PATCH] add forum link --- ralf/_posts/2020-12-14-provenance.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ralf/_posts/2020-12-14-provenance.md b/ralf/_posts/2020-12-14-provenance.md index 48fc93c..2f8c23c 100644 --- a/ralf/_posts/2020-12-14-provenance.md +++ b/ralf/_posts/2020-12-14-provenance.md @@ -1,6 +1,7 @@ --- title: "Pointers Are Complicated II, or: We need better language specs" categories: rust +forum: https://internals.rust-lang.org/t/pointers-are-complicated-ii-or-we-need-better-language-specs/13562 --- Some time ago, I wrote a blog post about how [there's more to a pointer than meets the eye]({% post_url 2018-07-24-pointers-and-bytes %}). @@ -270,7 +271,7 @@ Progress on these specification efforts is slow, though, in particular when it t I hope this post can raise awareness for the subtle problems optimizing compilers are facing, and convince some people that figuring out the specification of compiler IRs is an important and interesting problem to work on. :) That's all I have for today, thanks for sticking with me! -As usual, this post can be discussed in the Rust forums. +As usual, this post can be [discussed in the Rust forums](https://internals.rust-lang.org/t/pointers-are-complicated-ii-or-we-need-better-language-specs/13562). I am curious what your thoughts are on how we can build compilers that do not suffer from the issues I have discussed here. #### Footnotes -- 2.30.2