X-Git-Url: https://git.ralfj.de/web.git/blobdiff_plain/6961731dc7c9949e52a09852ed994f4906e2c714..9eacabff934cb184dde6aff93d8777c9d6622023:/personal/_posts/2016-01-09-the-scope-of-unsafe.md diff --git a/personal/_posts/2016-01-09-the-scope-of-unsafe.md b/personal/_posts/2016-01-09-the-scope-of-unsafe.md index 96a7eb4..967b4a3 100644 --- a/personal/_posts/2016-01-09-the-scope-of-unsafe.md +++ b/personal/_posts/2016-01-09-the-scope-of-unsafe.md @@ -16,7 +16,7 @@ What I am saying is that the scope of `unsafe` is larger than the `unsafe` block It turns out that the underlying reason for this observation is also a nice illustration for the concept of *semantic types* that comes up in my [work on formalizing Rust]({% post_url 2015-10-12-formalizing-rust %}) (or rather, its type system). Finally, this discussion will once again lead us to realize that we rely on our type systems to provide much more than just type safety. -**Update (Jan 11th):** Clarified the role of privacy; argued why `evil` is the problem. +**Update (2016-01-11):** Clarified the role of privacy; argued why `evil` is the problem.