urie
/
100-exercises-to-learn-rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix broken links (#47)

This commit is contained in:
Sympatron GmbH 2024-05-24 12:57:57 +02:00 committed by GitHub
parent eb0b4f75f0
commit 7a4fa2d1f4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
8 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
book/src/02_basic_calculator/01_integers.md
View File

@ -117,7 +117,7 @@ error[E0308]: mismatched types
| |
``` ```
We'll see how to convert between types [later in this course](../04_traits/08_from). We'll see how to convert between types [later in this course](../04_traits/09_from).
## References ## References
@ -134,5 +134,5 @@ behave.
We'll talk about operator overloading [later in the course](../04_traits/03_operator_overloading), after we've covered traits. We'll talk about operator overloading [later in the course](../04_traits/03_operator_overloading), after we've covered traits.
[^coercion]: There are some exceptions to this rule, mostly related to references, smart pointers and ergonomics. We'll [^coercion]: There are some exceptions to this rule, mostly related to references, smart pointers and ergonomics. We'll
cover those [later on](../04_traits/06_deref). cover those [later on](../04_traits/07_deref).
A mental model of "all conversions are explicit" will serve you well in the meantime. A mental model of "all conversions are explicit" will serve you well in the meantime.

2
book/src/02_basic_calculator/04_panics.md
View File

@ -1,6 +1,6 @@
# Panics # Panics
Let's go back to the `speed` function you wrote for the ["Variables" section](../02_variables/README.md). Let's go back to the `speed` function you wrote for the ["Variables" section](02_variables).
It probably looked something like this: It probably looked something like this:
```rust ```rust

2
book/src/02_basic_calculator/10_as_casting.md
View File

@ -92,7 +92,7 @@ It is also fairly limited: you can only rely on `as` casting
for primitive types and a few other special cases. for primitive types and a few other special cases.
When working with composite types, you'll have to rely on When working with composite types, you'll have to rely on
different conversion mechanisms ([fallible](../05_ticket_v2/13_try_from) different conversion mechanisms ([fallible](../05_ticket_v2/13_try_from)
and [infallible](../04_traits/08_from)), which we'll explore later on. and [infallible](../04_traits/09_from)), which we'll explore later on.
## References ## References

2
book/src/03_ticket_v1/05_encapsulation.md
View File

@ -38,7 +38,7 @@ let ticket = Ticket {
You've seen this in action in the previous exercise on visibility. You've seen this in action in the previous exercise on visibility.
We now need to provide one or more public **constructors**—i.e. static methods or functions that can be used We now need to provide one or more public **constructors**—i.e. static methods or functions that can be used
from outside the module to create a new instance of the struct. from outside the module to create a new instance of the struct.
Luckily enough we already have one: `Ticket::new`, as implemented in [a previous exercise](../02_validation/README.md). Luckily enough we already have one: `Ticket::new`, as implemented in [a previous exercise](02_validation).
## Accessor methods ## Accessor methods

2
book/src/03_ticket_v1/10_references_in_memory.md
View File

@ -49,6 +49,6 @@ They just point to a memory location, which _may_ be on the heap, but doesn't ha
- The exercise for this section is located in `exercises/03_ticket_v1/10_references_in_memory` - The exercise for this section is located in `exercises/03_ticket_v1/10_references_in_memory`
[^fat]: [Later in the course](../04_traits/05_str_slice) we'll talk about **fat pointers**, [^fat]: [Later in the course](../04_traits/06_str_slice) we'll talk about **fat pointers**,
i.e. pointers with additional metadata. As the name implies, they are larger than i.e. pointers with additional metadata. As the name implies, they are larger than
the pointers we discussed in this chapter, also known as **thin pointers**. the pointers we discussed in this chapter, also known as **thin pointers**.

2
book/src/04_traits/08_sized.md
View File

@ -6,7 +6,7 @@ From our previous [discussion on memory layouts](../03_ticket_v1/10_references_i
it would have been reasonable to expect `&str` to be represented as a single `usize` on it would have been reasonable to expect `&str` to be represented as a single `usize` on
the stack, a pointer. That's not the case though. `&str` stores some **metadata** next the stack, a pointer. That's not the case though. `&str` stores some **metadata** next
to the pointer: the length of the slice it points to. Going back to the example from to the pointer: the length of the slice it points to. Going back to the example from
[a previous section](05_str_slice.md): [a previous section](06_str_slice):
```rust ```rust
let mut s = String::with_capacity(5); let mut s = String::with_capacity(5);

2
book/src/05_ticket_v2/09_error_trait.md
View File

@ -22,7 +22,7 @@ that implements the `Error` trait.
pub trait Error: Debug + Display {} pub trait Error: Debug + Display {}
``` ```
You might recall the `:` syntax from [the `Sized` trait](../04_traits/07_sized.md)—it's used to specify **supertraits**. You might recall the `:` syntax from [the `Sized` trait](../04_traits/08_sized.md)—it's used to specify **supertraits**.
For `Error`, there are two supertraits: `Debug` and `Display`. If a type wants to implement `Error`, it must also For `Error`, there are two supertraits: `Debug` and `Display`. If a type wants to implement `Error`, it must also
implement `Debug` and `Display`. implement `Debug` and `Display`.

2
book/src/05_ticket_v2/13_try_from.md
View File

@ -1,6 +1,6 @@
# `TryFrom` and `TryInto` # `TryFrom` and `TryInto`
In the previous chapter we looked at the [`From` and `Into` traits](../04_traits/08_from.md), In the previous chapter we looked at the [`From` and `Into` traits](../04_traits/09_from.md),
Rust's idiomatic interfaces for **infallible** type conversions. Rust's idiomatic interfaces for **infallible** type conversions.
But what if the conversion is not guaranteed to succeed? But what if the conversion is not guaranteed to succeed?