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

fix(book): Correct type parameter naming convention to pascal case (#79) 

* fix(book): Correct type parameter naming convention to pascal case

* Update book/src/04_traits/05_trait_bounds.md

---------

Co-authored-by: Felix Pherry <182051.FELIX@klgroup.local>
Co-authored-by: Luca Palmieri <20745048+LukeMathWalker@users.noreply.github.com>
This commit is contained in:
Felix Pherry 2024-06-01 13:31:48 +07:00 committed by GitHub
parent ffb2f08b67
commit e99a15390e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -58,7 +58,7 @@ We can do better using **generics**.\
Generics allow us to write code that works with a **type parameter** instead of a concrete type: Generics allow us to write code that works with a **type parameter** instead of a concrete type:
```rust ```rust
fn print_if_even<T>(n: T) fn print_if_even<T>(n: T)
where where
T: IsEven + Debug T: IsEven + Debug
{ {
@ -125,7 +125,7 @@ body is present.
All the examples above used a **`where` clause** to specify trait bounds: All the examples above used a **`where` clause** to specify trait bounds:
```rust ```rust
fn print_if_even<T>(n: T) fn print_if_even<T>(n: T)
where where
T: IsEven + Debug T: IsEven + Debug
// ^^^^^^^^^^^^^^^^^ // ^^^^^^^^^^^^^^^^^
@ -160,7 +160,7 @@ fn print_if_even<Number: IsEven + Debug>(n: Number) {
It is actually **desirable** to use meaningful names when there are multiple type parameters at play or when the name It is actually **desirable** to use meaningful names when there are multiple type parameters at play or when the name
`T` doesn't convey enough information about the type's role in the function. `T` doesn't convey enough information about the type's role in the function.
Maximize clarity and readability when naming type parameters, just as you would with variables or function parameters. Maximize clarity and readability when naming type parameters, just as you would with variables or function parameters.
Follow Rust's conventions though: use camel case for type parameter names. Follow Rust's conventions, though: use [upper camel case for type parameter names](https://rust-lang.github.io/api-guidelines/naming.html#casing-conforms-to-rfc-430-c-case).
## The function signature is king ## The function signature is king