mirror of
https://github.com/mainmatter/100-exercises-to-learn-rust
synced 2024-12-26 21:58:49 +01:00
Fix: typos (#84)
Co-authored-by: Felix Pherry <182051.FELIX@klgroup.local>
This commit is contained in:
parent
e99a15390e
commit
056611ac1c
1 changed files with 1 additions and 1 deletions
|
@ -7,7 +7,7 @@ pass it to the `panic!` macro.\
|
||||||
This is a (rudimentary) example of **error reporting**: transforming an error type into a representation that can be
|
This is a (rudimentary) example of **error reporting**: transforming an error type into a representation that can be
|
||||||
shown to a user, a service operator, or a developer.
|
shown to a user, a service operator, or a developer.
|
||||||
|
|
||||||
It's not practical for each Rust developer to come up with their own error reporting strategy: it'd a waste of time
|
It's not practical for each Rust developer to come up with their own error reporting strategy: it'd be a waste of time
|
||||||
and it wouldn't compose well across projects.
|
and it wouldn't compose well across projects.
|
||||||
That's why Rust provides the `std::error::Error` trait.
|
That's why Rust provides the `std::error::Error` trait.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue