From fe7cf0aac45c68ceaad2c59cba6f0270c06e1e6c Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Tue, 18 Jul 2017 09:47:11 -0700 Subject: [PATCH 1/1] ammendments go into the forum --- personal/_posts/2017-07-17-types-as-contracts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/personal/_posts/2017-07-17-types-as-contracts.md b/personal/_posts/2017-07-17-types-as-contracts.md index 125a1aa..d11e77b 100644 --- a/personal/_posts/2017-07-17-types-as-contracts.md +++ b/personal/_posts/2017-07-17-types-as-contracts.md @@ -395,7 +395,7 @@ Congratulations! You have reached the end of this blog post. Thanks a lot for reading. If you have any comments, please raise them -- the entire purpose of this post is to get the proposal out there so that we can see if this approach can suit the needs of Rust programmers and compiler writers alike. -If there are explanations you think are missing or confusing, please bring that up as well; I may then update this post accordingly. +If there are explanations you think are missing or confusing, please bring that up as well; I may then update this post accordingly or add a note in the [forum](https://internals.rust-lang.org/t/types-as-contracts/5562) for any ammendments that turned out to be necessary. The concrete proposal will sure need some fixing here and there, but my hope is that the general approach of a contract-like, type-driven validation mechanism ends up being useful. So, keep the comments flowing -- and safe hacking. -- 2.30.2