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

refine wording 

to a string sounds awkward,  to string is, probably, softer on the eye.
This commit is contained in:
Bulat Musin 2018-01-11 09:52:09 +03:00 committed by GitHub
parent 1adedabe22
commit 1d2c61323e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -917,7 +917,7 @@ Reasonable people can disagree over whether this code is better than the code
that uses combinators, but if you aren't familiar with the combinator approach,
this code looks simpler to read to me. It uses explicit case analysis with
`match` and `if let`. If an error occurs, it simply stops executing the
function and returns the error (by converting it to a string).
function and returns the error (by converting it to string).
Isn't this a step backwards though? Previously, we said that the key to
ergonomic error handling is reducing explicit case analysis, yet we've reverted