X-Git-Url: https://git.ralfj.de/web.git/blobdiff_plain/9131d1a0288847311e6d15fb8c0cda54d6815d7f..refs/heads/master:/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 ec9fde0..967b4a3 100644 --- a/personal/_posts/2016-01-09-the-scope-of-unsafe.md +++ b/personal/_posts/2016-01-09-the-scope-of-unsafe.md @@ -2,6 +2,8 @@ title: The Scope of Unsafe categories: research rust reddit: /rust/comments/4065l2/the_scope_of_unsafe/ +license: CC BY-SA 4.0 +license-url: https://creativecommons.org/licenses/by-sa/4.0/ --- I'd like to talk about an important aspect of dealing with unsafe code, that still regularly seems to catch people on the wrong foot: @@ -14,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.