From: Ralf Jung Date: Wed, 15 Jul 2020 11:10:47 +0000 (+0200) Subject: add forum link X-Git-Url: https://git.ralfj.de/web.git/commitdiff_plain/280f556bac4782d9ec7251b8e5e3e0c33d20c29d?hp=1afcf299355caf931b823f9473da59e1835d9f8e add forum link --- diff --git a/personal/_posts/2020-07-15-unused-data.md b/personal/_posts/2020-07-15-unused-data.md index 16068e8..afdfff9 100644 --- a/personal/_posts/2020-07-15-unused-data.md +++ b/personal/_posts/2020-07-15-unused-data.md @@ -1,6 +1,7 @@ --- title: "Why even unused data needs to be valid" categories: rust +forum: https://internals.rust-lang.org/t/why-even-unused-data-needs-to-be-valid/12734 --- The Rust compiler has a few assumptions that it makes about the behavior of all code. @@ -9,7 +10,7 @@ Since Rust is a safe-by-default language, programmers usually do not have to wor but authors of `unsafe` code are themselves responsible for upholding these requirements. Those assumptions are [listed in the Rust reference](https://doc.rust-lang.org/reference/behavior-considered-undefined.html). -The one that seems to be most surprising to many people is the clause which says that unsafe code may not *produce* "[...] an invalid value, even in private fields and locals". +The one that seems to be most surprising to many people is the clause which says that Rust code may not *produce* "[...] an invalid value, even in private fields and locals". The reference goes on to explain that "*producing* a value happens any time a value is assigned to or read from a place, passed to a function/primitive operation or returned from a function/primitive operation". In other words, even just *constructing*, for example, an invalid `bool`, is Undefined Behavior---no matter whether that `bool` is ever actually "used" by the program. The purpose of this post is to explain why that rule is so strict. @@ -85,4 +86,4 @@ But this means our hands are pretty much tied: since we cannot take into account To support inlining and outlining, we also do not want the function boundary to be relevant, which ultimately leads us to the rule that Rust requires today: whenever data of a given type is *produced* anywhere, the data needs to be valid for that type. I hope this post was helpful in explaining why Undefined Behavior in Rust is defined the way it is. -As usual, if you have any comments or questions, let me know in the forums. +As usual, if you have any comments or questions, let me know in the [forums](https://internals.rust-lang.org/t/why-even-unused-data-needs-to-be-valid/12734).