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

Add CI job to verify that we have no broken links. (#50)

Browse Source 
Fix all broken links.
This commit is contained in:
Luca Palmieri
2024-05-24 16:45:59 +02:00
committed by GitHub
parent 6d707bb32d
commit f388b2a6c3
11 changed files with 43 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
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/09_from).
We'll see how to convert between types [later in this course](../04_traits/09_from.md).
## References
@@ -131,8 +131,8 @@ We'll see how to convert between types [later in this course](../04_traits/09_fr
[^traits]: Rust doesn't let you define custom operators, but it puts you in control of how the built-in operators
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.md), after we've covered traits.
[^coercion]: There are some exceptions to this rule, mostly related to references, smart pointers and ergonomics. We'll
cover those [later on](../04_traits/07_deref).
cover those [later on](../04_traits/07_deref.md).
A mental model of "all conversions are explicit" will serve you well in the meantime.

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

@@ -1,6 +1,6 @@
# Panics
Let's go back to the `speed` function you wrote for the ["Variables" section](02_variables).
Let's go back to the `speed` function you wrote for the ["Variables" section](02_variables.md).
It probably looked something like this:
```rust
@@ -38,7 +38,7 @@ fn main() {
}
```
There are other mechanisms to work with recoverable errors in Rust, which [we'll cover later](../05_ticket_v2/06_fallibility).
There are other mechanisms to work with recoverable errors in Rust, which [we'll cover later](../05_ticket_v2/06_fallibility.md).
For the time being we'll stick with panics as a brutal but simple stopgap solution.
## References

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

@@ -82,7 +82,7 @@ error: literal out of range for `i8`
As a rule of thumb, be quite careful with `as` casting.
Use it _exclusively_ for going from a smaller type to a larger type.
To convert from a larger to smaller integer type, rely on the
[*fallible* conversion machinery](../05_ticket_v2/13_try_from) that we'll
[*fallible* conversion machinery](../05_ticket_v2/13_try_from.md) that we'll
explore later in the course.
### Limitations
@@ -91,8 +91,8 @@ Surprising behaviour is not the only downside of `as` casting.
It is also fairly limited: you can only rely on `as` casting
for primitive types and a few other special cases.
When working with composite types, you'll have to rely on
different conversion mechanisms ([fallible](../05_ticket_v2/13_try_from)
and [infallible](../04_traits/09_from)), which we'll explore later on.
different conversion mechanisms ([fallible](../05_ticket_v2/13_try_from.md)
and [infallible](../04_traits/09_from.md)), which we'll explore later on.
## References