diff options
| author | Corey Farwell <coreyf@rwell.org> | 2017-12-06 09:35:37 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-12-06 09:35:37 -0500 |
| commit | e5fd52bed2f51eb336fd95297ec12dc74f24fcae (patch) | |
| tree | 28ac4bbdc67ac3ac14de37322b1505e503fa521e /src/libcore | |
| parent | f5e4aa2a80bf41c307fb479f1c9a187a9413dec1 (diff) | |
| parent | 893474ea6d16497b23503582f5b85be2ea2bab0b (diff) | |
| download | rust-e5fd52bed2f51eb336fd95297ec12dc74f24fcae.tar.gz rust-e5fd52bed2f51eb336fd95297ec12dc74f24fcae.zip | |
Rollup merge of #46431 - steveklabnik:gh42725, r=QuietMisdreavus
Mention the name of ? in Result's docs Fixes #42725 or at least, this is the best we can really do. #35946 is tracking better errors already, so that should cover the other part of it.
Diffstat (limited to 'src/libcore')
| -rw-r--r-- | src/libcore/result.rs | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/src/libcore/result.rs b/src/libcore/result.rs index db5bffced10..959935242dc 100644 --- a/src/libcore/result.rs +++ b/src/libcore/result.rs @@ -153,12 +153,12 @@ //! } //! ``` //! -//! # The `?` syntax +//! # The question mark operator, `?` //! //! When writing code that calls many functions that return the -//! [`Result`] type, the error handling can be tedious. The [`?`] -//! syntax hides some of the boilerplate of propagating errors up the -//! call stack. +//! [`Result`] type, the error handling can be tedious. The question mark +//! operator, [`?`], hides some of the boilerplate of propagating errors +//! up the call stack. //! //! It replaces this: //! |
