From: Ralf Jung Date: Wed, 13 Apr 2022 23:51:03 +0000 (-0400) Subject: update PNVI-ae-udi paper URL X-Git-Url: https://git.ralfj.de/web.git/commitdiff_plain/107de6de7127f051e9f6c4a01b80d02483594794?hp=94d0b1594ae4fffbf2999b59c411f6755f46d47a update PNVI-ae-udi paper URL --- diff --git a/personal/_posts/2022-04-11-provenance-exposed.md b/personal/_posts/2022-04-11-provenance-exposed.md index e5560e2..6ab04f5 100644 --- a/personal/_posts/2022-04-11-provenance-exposed.md +++ b/personal/_posts/2022-04-11-provenance-exposed.md @@ -328,7 +328,7 @@ Compositionality at its finest! I have talked a lot about my vision for "solving" pointer provenance in Rust. What about other languages? -As you might have heard, C is moving towards making [PNVI-ae-udi](http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2577.pdf) an official recommendation for how to interpret the C memory model. +As you might have heard, C is moving towards making [PNVI-ae-udi](http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2676.pdf) an official recommendation for how to interpret the C memory model. With C having so much more legacy code to care about and many more stakeholders than Rust does, this is an impressive achievement! How does it compare to all I said above?