mirror of
https://github.com/google/comprehensive-rust.git
synced 2025-04-22 07:47:44 +02:00
Rework generic fn examples to show monomorphized versions (#2671)
Something I always do when covering generic fns is I like to show the monomorphized versions of `pick` to make it clear to students what generics are doing behind the scenes. In my most recent class I tried going the other way around, showing the monomorphized versions first to more clearly motivate what generics are used for, and I liked the way it went. I think motivating generics by first showing code duplication and then showing how generics allow us to de-duplicate makes for a good teaching flow, and I think it also helps make things clearer to students coming from more dynamic languages that don't have an equivalent to generics. I also changed the `pick` fns to take a `bool` as the first argument because I think that makes things slightly clearer/cleaner, but I'm not married to that change either.
This commit is contained in:
parent
8ed932f65c
commit
7f45460811
@ -8,26 +8,48 @@ Rust supports generics, which lets you abstract algorithms or data structures
|
|||||||
(such as sorting or a binary tree) over the types used or stored.
|
(such as sorting or a binary tree) over the types used or stored.
|
||||||
|
|
||||||
```rust,editable
|
```rust,editable
|
||||||
/// Pick `even` or `odd` depending on the value of `n`.
|
fn pick<T>(cond: bool, left: T, right: T) -> T {
|
||||||
fn pick<T>(n: i32, even: T, odd: T) -> T {
|
if cond {
|
||||||
if n % 2 == 0 {
|
left
|
||||||
even
|
|
||||||
} else {
|
} else {
|
||||||
odd
|
right
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
fn main() {
|
fn main() {
|
||||||
println!("picked a number: {:?}", pick(97, 222, 333));
|
println!("picked a number: {:?}", pick(true, 222, 333));
|
||||||
println!("picked a string: {:?}", pick(28, "dog", "cat"));
|
println!("picked a string: {:?}", pick(false, 'L', 'R'));
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
<details>
|
<details>
|
||||||
|
|
||||||
|
- It can be helpful to show the monomorphized versions of `pick`, either before
|
||||||
|
talking about the generic `pick` in order to show how generics can reduce code
|
||||||
|
duplication, or after talking about generics to show how monomorphization
|
||||||
|
works.
|
||||||
|
|
||||||
|
```rust
|
||||||
|
fn pick_i32(cond: bool, left: i32, right: i32) -> i32 {
|
||||||
|
if cond {
|
||||||
|
left
|
||||||
|
} else {
|
||||||
|
right
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
|
fn pick_char(cond: bool, left: char, right: char) -> char {
|
||||||
|
if cond {
|
||||||
|
left
|
||||||
|
} else {
|
||||||
|
right
|
||||||
|
}
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
- Rust infers a type for T based on the types of the arguments and return value.
|
- Rust infers a type for T based on the types of the arguments and return value.
|
||||||
|
|
||||||
- In this example we only use the primitive types `i32` and `&str` for `T`, but
|
- In this example we only use the primitive types `i32` and `char` for `T`, but
|
||||||
we can use any type here, including user-defined types:
|
we can use any type here, including user-defined types:
|
||||||
|
|
||||||
```rust,ignore
|
```rust,ignore
|
||||||
|
Loading…
x
Reference in New Issue
Block a user