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

2
book/src/04_traits/05_trait_bounds.md
View File

@@ -166,7 +166,7 @@ Follow Rust's conventions though: use camel case for type parameter names.
You may wonder why we need trait bounds at all. Can't the compiler infer the required traits from the function's body?
It could, but it won't.
The rationale is the same as for [explicit type annotations on function parameters](../02_basic_calculator/02_variables#function-arguments-are-variables):
The rationale is the same as for [explicit type annotations on function parameters](../02_basic_calculator/02_variables.md#function-arguments-are-variables):
each function signature is a contract between the caller and the callee, and the terms must be explicitly stated.
This allows for better error messages, better documentation, less unintentional breakages across versions,
and faster compilation times.