Format all Markdown files with dprint (#1157)

This is the result of running `dprint fmt` after removing `src/` from
the list of excluded directories.

This also reformats the Rust code: we might want to tweak this a bit in
the future since some of the changes removes the hand-formatting. Of
course, this formatting can be seen as a mis-feature, so maybe this is
good overall.

Thanks to mdbook-i18n-helpers 0.2, the POT file is nearly unchanged
after this, meaning that all existing translations remain valid! A few
messages were changed because of stray whitespace characters:

     msgid ""
     "Slices always borrow from another object. In this example, `a` has to remain "
    -"'alive' (in scope) for at least as long as our slice. "
    +"'alive' (in scope) for at least as long as our slice."
     msgstr ""

The formatting is enforced in CI and we will have to see how annoying
this is in practice for the many contributors. If it becomes annoying,
we should look into fixing dprint/check#11 so that `dprint` can annotate
the lines that need fixing directly, then I think we can consider more
strict formatting checks.

I added more customization to `rustfmt.toml`. This is to better emulate
the dense style used in the course:

- `max_width = 85` allows lines to take up the full width available in
our code blocks (when taking margins and the line numbers into account).
- `wrap_comments = true` ensures that we don't show very long comments
in the code examples. I edited some comments to shorten them and avoid
unnecessary line breaks — please trim other unnecessarily long comments
when you see them! Remember we're writing code for slides 😄
- `use_small_heuristics = "Max"` allows for things like struct literals
and if-statements to take up the full line width configured above.

The formatting settings apply to all our Rust code right now — I think
we could improve this with https://github.com/dprint/dprint/issues/711
which lets us add per-directory `dprint` configuration files. However,
the `inherit: true` setting is not yet implemented (as far as I can
tell), so a nested configuration file will have to copy most or all of
the top-level file.

src/concurrency/send-sync/examples.md

@@ -4,12 +4,12 @@
 
 Most types you come across are `Send + Sync`:
 
-* `i8`, `f32`, `bool`, `char`, `&str`, ...
-* `(T1, T2)`, `[T; N]`, `&[T]`, `struct { x: T }`, ...
-* `String`, `Option<T>`, `Vec<T>`, `Box<T>`, ...
-* `Arc<T>`: Explicitly thread-safe via atomic reference count.
-* `Mutex<T>`: Explicitly thread-safe via internal locking.
-* `AtomicBool`, `AtomicU8`, ...: Uses special atomic instructions.
+- `i8`, `f32`, `bool`, `char`, `&str`, ...
+- `(T1, T2)`, `[T; N]`, `&[T]`, `struct { x: T }`, ...
+- `String`, `Option<T>`, `Vec<T>`, `Box<T>`, ...
+- `Arc<T>`: Explicitly thread-safe via atomic reference count.
+- `Mutex<T>`: Explicitly thread-safe via internal locking.
+- `AtomicBool`, `AtomicU8`, ...: Uses special atomic instructions.
 
 The generic types are typically `Send + Sync` when the type parameters are
 `Send + Sync`.
@@ -19,23 +19,23 @@ The generic types are typically `Send + Sync` when the type parameters are
 These types can be moved to other threads, but they're not thread-safe.
 Typically because of interior mutability:
 
-* `mpsc::Sender<T>`
-* `mpsc::Receiver<T>`
-* `Cell<T>`
-* `RefCell<T>`
+- `mpsc::Sender<T>`
+- `mpsc::Receiver<T>`
+- `Cell<T>`
+- `RefCell<T>`
 
 ## `!Send + Sync`
 
 These types are thread-safe, but they cannot be moved to another thread:
 
-* `MutexGuard<T: Sync>`: Uses OS level primitives which must be deallocated on the
-  thread which created them.
+- `MutexGuard<T: Sync>`: Uses OS level primitives which must be deallocated on
+  the thread which created them.
 
 ## `!Send + !Sync`
 
 These types are not thread-safe and cannot be moved to other threads:
 
-* `Rc<T>`: each `Rc<T>` has a reference to an `RcBox<T>`, which contains a
+- `Rc<T>`: each `Rc<T>` has a reference to an `RcBox<T>`, which contains a
   non-atomic reference count.
-* `*const T`, `*mut T`: Rust assumes raw pointers may have special
-  concurrency considerations.
+- `*const T`, `*mut T`: Rust assumes raw pointers may have special concurrency
+  considerations.

src/concurrency/send-sync/sync.md

@@ -11,8 +11,14 @@ More precisely, the definition is:
 
 <details>
 
-This statement is essentially a shorthand way of saying that if a type is thread-safe for shared use, it is also thread-safe to pass references of it across threads.
+This statement is essentially a shorthand way of saying that if a type is
+thread-safe for shared use, it is also thread-safe to pass references of it
+across threads.
 
-This is because if a type is Sync it means that it can be shared across multiple threads without the risk of data races or other synchronization issues, so it is safe to move it to another thread. A reference to the type is also safe to move to another thread, because the data it references can be accessed from any thread safely.
+This is because if a type is Sync it means that it can be shared across multiple
+threads without the risk of data races or other synchronization issues, so it is
+safe to move it to another thread. A reference to the type is also safe to move
+to another thread, because the data it references can be accessed from any
+thread safely.
 
 </details>