rust
/
book
mirror of https://github.com/rust-lang/book
1
0
Fork 0
Code Issues Releases Wiki Activity

Merge pull request #1107 from bmusin/patch-3 

fix typo
This commit is contained in:
Carol (Nichols || Goulding) 2018-01-12 16:04:14 -05:00 committed by GitHub
parent 37221d239e 4475811984
commit d75460f536
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
first-edition/src/error-handling.md
View File

@ -647,9 +647,9 @@ a bit nicer to deal with, since it will show your message instead of
My advice boils down to this: use good judgment. There's a reason why the words
“never do X” or “Y is considered harmful” don't appear in my writing. There are
trade offs to all things, and it is up to you as the programmer to determine
trade-offs to all things, and it is up to you as the programmer to determine
what is acceptable for your use cases. My goal is only to help you evaluate
trade offs as accurately as possible.
trade-offs as accurately as possible.
Now that we've covered the basics of error handling in Rust, and
explained unwrapping, let's start exploring more of the standard