github_mirrors/rust-book-cn
1
0
Fork 0
mirror of https://github.com/rust-lang-cn/book-cn.git synced 2025-01-23 23:50:25 +08:00
Code Issues Packages Projects Releases Wiki Activity

Make notes since we now know 1.14 will have the question mark

Browse Source
This commit is contained in:
Carol (Nichols || Goulding) 2016-10-18 18:33:35 -04:00
parent ee823778b1
commit 234e75847a
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.travis.yml
View File

@ -4,9 +4,9 @@ cache: cargo
rust:
- nightly
# - beta
# ^ to be changed once question_mark is in beta
# ^ to be changed once question_mark is in beta: 1.14
# - stable
# ^ to be changed once question_mark becomes stable
# ^ to be changed once question_mark becomes stable: 1.14
before_script:
- (cargo install mdbook || true)
script:

6
src/ch09-02-recoverable-errors-with-result.md
View File

@ -239,9 +239,9 @@ username as a `String` inside the `Ok` variant, so that is our success type.
This is a very common way of handling errors: propagate them upward until
you're ready to deal with them. This pattern is so common in Rust that there is
a macro for it, `try!`, and as of Rust 1.XX <!-- We will fill this in once the
question mark is released in a stable version; we don't know for sure which
version it will be yet /Carol -->, dedicated syntax for it: the question mark
a macro for it, `try!`, and as of Rust 1.14 <!-- 1.14 has not been released as
a stable version yet, but that's the version the question mark operator will be
released in /Carol -->, dedicated syntax for it: the question mark
operator. We could have written the code in Listing 9-5 using the `try!` macro,
as in Listing 9-6, and it would have the same functionality as the `match`
expressions: