From cec15cc453a7bf52450bc2b8eb0de77ae129459a Mon Sep 17 00:00:00 2001 From: Roberto Vidal Date: Thu, 13 Dec 2018 15:42:06 +0100 Subject: [PATCH] Fixes outdated links to docs --- src/c-tips/index.md | 2 +- src/concurrency/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/c-tips/index.md b/src/c-tips/index.md index 0f5184a..14d7eea 100644 --- a/src/c-tips/index.md +++ b/src/c-tips/index.md @@ -203,7 +203,7 @@ In Rust, pointers (called [_raw pointers_]) exist but are only used in specific circumstances, as dereferencing them is always considered `unsafe` -- Rust cannot provide its usual guarantees about what might be behind the pointer. -[_raw pointers_]: https://doc.rust-lang.org/book/second-edition/ch19-01-unsafe-rust.html#dereferencing-a-raw-pointer +[_raw pointers_]: https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html#dereferencing-a-raw-pointer In most cases, we instead use _references_, indicated by the `&` symbol, or _mutable references_, indicated by `&mut`. References behave similarly to diff --git a/src/concurrency/index.md b/src/concurrency/index.md index 9749ad6..5d432f9 100644 --- a/src/concurrency/index.md +++ b/src/concurrency/index.md @@ -52,7 +52,7 @@ because without taking special care, you might trigger a race condition, where your access to the variable is interrupted halfway through by an interrupt which also accesses that variable. -[`static mut`]: https://doc.rust-lang.org/book/second-edition/ch19-01-unsafe-rust.html#accessing-or-modifying-a-mutable-static-variable +[`static mut`]: https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html#accessing-or-modifying-a-mutable-static-variable For an example of how this behaviour can cause subtle errors in your code, consider an embedded program which counts rising edges of some input signal