Skip to content

Commit 893474e

Browse files
committed
Mention the name of ? in Result's docs
Fixes rust-lang#42725 or at least, this is the best we can really do. rust-lang#35946 is tracking better errors already, so that should cover the other part of it.
1 parent e3ed212 commit 893474e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/libcore/result.rs

+4-4
Original file line numberDiff line numberDiff line change
@@ -153,12 +153,12 @@
153153
//! }
154154
//! ```
155155
//!
156-
//! # The `?` syntax
156+
//! # The question mark operator, `?`
157157
//!
158158
//! When writing code that calls many functions that return the
159-
//! [`Result`] type, the error handling can be tedious. The [`?`]
160-
//! syntax hides some of the boilerplate of propagating errors up the
161-
//! call stack.
159+
//! [`Result`] type, the error handling can be tedious. The question mark
160+
//! operator, [`?`], hides some of the boilerplate of propagating errors
161+
//! up the call stack.
162162
//!
163163
//! It replaces this:
164164
//!

0 commit comments

Comments
 (0)