Skip to content

fix: change some_string to some_char #101

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SergioRibera merged 1 commit into from
Apr 13, 2026
Merged

fix: change some_string to some_char #101

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/ch06-01-defining-an-enum.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -267,8 +267,8 @@ de usar valores `Option` para contener tipos de números y tipos de strings:
{{#rustdoc_include ../listings/ch06-enums-and-pattern-matching/no-listing-06-option-examples/src/main.rs:here}}
```

El tipo de `some_number` es `Option<i32>`. El tipo de `some_string` es
`Option<String>`, que es un tipo diferente. Rust puede inferir estos tipos
El tipo de `some_number` es `Option<i32>`. El tipo de `some_char` es
`Option<char>`, que es un tipo diferente. Rust puede inferir estos tipos
porque hemos especificado un valor dentro de la variante `Some`. Para
`absent_number`, Rust requiere que anotemos el tipo general `Option`: el
compilador no puede inferir el tipo que tendrá la variante `Some` correspondiente
Expand Down
Loading