about summary refs log tree commit diff
path: root/src/libcore
diff options
context:
space:
mode:
authorsteveklabnik <steve@steveklabnik.com>2017-12-01 13:00:45 -0500
committersteveklabnik <steve@steveklabnik.com>2017-12-05 10:07:51 -0500
commit893474ea6d16497b23503582f5b85be2ea2bab0b (patch)
tree2b0a540a4e38b02dd2d470060201f63149e9ce4d /src/libcore
parente3ed21272d5f50c37c09f2a7f06c40f56b6ac298 (diff)
downloadrust-893474ea6d16497b23503582f5b85be2ea2bab0b.tar.gz
rust-893474ea6d16497b23503582f5b85be2ea2bab0b.zip
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.rs8
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:
 //!