-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Mention the name of ? in Result's docs #46431
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
Random assignment from docs team — r? @QuietMisdreavus |
src/libcore/result.rs
Outdated
//! 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, [`?`], syntax hides some of the boilerplate of propagating errors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The question mark operator,
?
, syntax hides some...
Seems like it would read better without "syntax" there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated!
Is "question mark operator" really the official term now? I much prefer "try operator". |
The reference currently expands it to "question mark" operator, at least. |
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.
@bors r+ rollup Thanks! Any farther discussion of what to call the |
📌 Commit 893474e has been approved by |
…avus 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.
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.