From fde9f5bd57b6785426ade89d2bd4a9a342b4301d Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Fri, 11 Aug 2017 16:04:30 -0700 Subject: [PATCH 1/1] forum link --- ralf/_posts/2017-08-11-types-as-contracts-evaluation.md | 1 + 1 file changed, 1 insertion(+) diff --git a/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md b/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md index e06ccc0..b6fe54a 100644 --- a/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md +++ b/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md @@ -1,6 +1,7 @@ --- title: "Types as Contracts: Implementation and Evaluation" categories: internship rust +forum: https://internals.rust-lang.org/t/https-www-ralfj-de-blog-2017-08-11-types-as-contracts-evaluation-html/5753 --- Some weeks ago, I described [Types as Contracts]({{ site.baseurl }}{% post_url 2017-07-17-types-as-contracts %}) as an approach for how to go about defining Rust's aliasing-related [undefined behavior]({{ site.baseurl }}{% post_url 2017-07-14-undefined-behavior %}). -- 2.30.2