From f75817ae2e56dd06d45ab8b335a7d27fe9544567 Mon Sep 17 00:00:00 2001 From: Chris Krycho Date: Mon, 16 Dec 2024 10:19:59 -0700 Subject: [PATCH] =?UTF-8?q?Ch.=2020:=20conclude=20=C2=A701=20with=20a=20re?= =?UTF-8?q?ference=20to=20the=20Rustonomicon?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- src/ch20-01-unsafe-rust.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/ch20-01-unsafe-rust.md b/src/ch20-01-unsafe-rust.md index 8796483a4b..7d4d8d8ca5 100644 --- a/src/ch20-01-unsafe-rust.md +++ b/src/ch20-01-unsafe-rust.md @@ -534,6 +534,9 @@ annotation makes it easier to track down the source of problems when they occur. Whenever you write unsafe code, you can use Miri to help you be more confident that the code you have written upholds Rust’s rules. +For a much deeper exploration of how to work effectively with unsafe Rust, read +Rust’s official guide to the subject, the [Rustonomicon][nomicon]. + [dangling-references]: ch04-02-references-and-borrowing.html#dangling-references [differences-between-variables-and-constants]: ch03-01-variables-and-mutability.html#constants [extensible-concurrency-with-the-sync-and-send-traits]: ch16-04-extensible-concurrency-sync-and-send.html#extensible-concurrency-with-the-sync-and-send-traits @@ -541,3 +544,4 @@ that the code you have written upholds Rust’s rules. [reference]: ../reference/items/unions.html [miri]: https://github.com/rust-lang/miri [nightly]: appendix-07-nightly-rust.html +[nomicon]: https://doc.rust-lang.org/nomicon/