From 4828c88af6132085c709db79500ac130669f72e2 Mon Sep 17 00:00:00 2001 From: Pascal Hertleif Date: Sat, 12 Sep 2015 12:13:24 +0200 Subject: [PATCH] Nomicon: Fix Links The style `[name][]` does not work with Pandoc, whereas `[name]` does. I hope hoedown accepts this as well. --- src/doc/nomicon/destructors.md | 2 +- src/doc/nomicon/meet-safe-and-unsafe.md | 4 ++-- src/doc/nomicon/other-reprs.md | 2 +- src/doc/nomicon/safe-unsafe-meaning.md | 4 ++-- src/doc/nomicon/send-and-sync.md | 2 +- src/doc/nomicon/transmutes.md | 2 +- 6 files changed, 8 insertions(+), 8 deletions(-) diff --git a/src/doc/nomicon/destructors.md b/src/doc/nomicon/destructors.md index 4492e2a92fa..91abdab9778 100644 --- a/src/doc/nomicon/destructors.md +++ b/src/doc/nomicon/destructors.md @@ -52,7 +52,7 @@ impl Drop for Box { ``` and this works fine because when Rust goes to drop the `ptr` field it just sees -a [Unique][] that has no actual `Drop` implementation. Similarly nothing can +a [Unique] that has no actual `Drop` implementation. Similarly nothing can use-after-free the `ptr` because when drop exits, it becomes inacessible. However this wouldn't work: diff --git a/src/doc/nomicon/meet-safe-and-unsafe.md b/src/doc/nomicon/meet-safe-and-unsafe.md index 15e49c747b8..52582e8750b 100644 --- a/src/doc/nomicon/meet-safe-and-unsafe.md +++ b/src/doc/nomicon/meet-safe-and-unsafe.md @@ -60,8 +60,8 @@ Unlike C, Undefined Behaviour is pretty limited in scope in Rust. All the core language cares about is preventing the following things: * Dereferencing null or dangling pointers -* Reading [uninitialized memory][] -* Breaking the [pointer aliasing rules][] +* Reading [uninitialized memory] +* Breaking the [pointer aliasing rules] * Producing invalid primitive values: * dangling/null references * a `bool` that isn't 0 or 1 diff --git a/src/doc/nomicon/other-reprs.md b/src/doc/nomicon/other-reprs.md index 93ef2c13cdf..71da743f35d 100644 --- a/src/doc/nomicon/other-reprs.md +++ b/src/doc/nomicon/other-reprs.md @@ -26,7 +26,7 @@ still consumes a byte of space. * DSTs, tuples, and tagged unions are not a concept in C and as such are never FFI safe. -* **If the type would have any [drop flags][], they will still be added** +* **If the type would have any [drop flags], they will still be added** * This is equivalent to one of `repr(u*)` (see the next section) for enums. The chosen size is the default enum size for the target platform's C ABI. Note that diff --git a/src/doc/nomicon/safe-unsafe-meaning.md b/src/doc/nomicon/safe-unsafe-meaning.md index e9037b56ff9..3cb02d31b17 100644 --- a/src/doc/nomicon/safe-unsafe-meaning.md +++ b/src/doc/nomicon/safe-unsafe-meaning.md @@ -35,7 +35,7 @@ unchecked contracts: There is also `#[unsafe_no_drop_flag]`, which is a special case that exists for historical reasons and is in the process of being phased out. See the section on -[drop flags][] for details. +[drop flags] for details. Some examples of unsafe functions: @@ -44,7 +44,7 @@ Some examples of unsafe functions: * `ptr::offset` is an intrinsic that invokes Undefined Behaviour if it is not "in bounds" as defined by LLVM. * `mem::transmute` reinterprets some value as having the given type, - bypassing type safety in arbitrary ways. (see [conversions][] for details) + bypassing type safety in arbitrary ways. (see [conversions] for details) * All FFI functions are `unsafe` because they can do arbitrary things. C being an obvious culprit, but generally any language can do something that Rust isn't happy about. diff --git a/src/doc/nomicon/send-and-sync.md b/src/doc/nomicon/send-and-sync.md index 8724b97546e..9ab60d03fca 100644 --- a/src/doc/nomicon/send-and-sync.md +++ b/src/doc/nomicon/send-and-sync.md @@ -10,7 +10,7 @@ captures this through the `Send` and `Sync` traits. Send and Sync are fundamental to Rust's concurrency story. As such, a substantial amount of special tooling exists to make them work right. First and -foremost, they're [unsafe traits][]. This means that they are unsafe to +foremost, they're [unsafe traits]. This means that they are unsafe to implement, and other unsafe code can assume that they are correctly implemented. Since they're *marker traits* (they have no associated items like methods), correctly implemented simply means that they have the intrinsic diff --git a/src/doc/nomicon/transmutes.md b/src/doc/nomicon/transmutes.md index f19dda0d8b8..2b34ad0a9fa 100644 --- a/src/doc/nomicon/transmutes.md +++ b/src/doc/nomicon/transmutes.md @@ -21,7 +21,7 @@ same size. The ways to cause Undefined Behaviour with this are mind boggling. * No you can't do it * No you're not special * Transmuting to a reference without an explicitly provided lifetime - produces an [unbounded lifetime][] + produces an [unbounded lifetime] `mem::transmute_copy` somehow manages to be *even more* wildly unsafe than this. It copies `size_of` bytes out of an `&T` and interprets them as a `U`.