Uh oh!
There was an error while loading. Please reload this page.
docs: make the description of Result::map_or more clear - #70760
Conversation
rust-highfive
commented
Apr 4, 2020
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @joshtriplett (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
Dylan-DPC-zz
commented
Apr 5, 2020
@bors r+ rollup |
bors
commented
Apr 5, 2020
📌 Commit b4f416d has been approved by |
Uh oh!
There was an error while loading. Please reload this page.
Rollup of 5 pull requests Successful merges: - rust-lang#70558 (Fix some aliasing issues in Vec) - rust-lang#70760 (docs: make the description of Result::map_or more clear) - rust-lang#70769 (Miri: remove an outdated FIXME) - rust-lang#70776 (clarify comment in RawVec::into_box) - rust-lang#70806 (fix Miri assignment sanity check) Failed merges: r? @ghost
The documentation of
Result::map_oris very unclear and confusing, probably because it was copied straight fromOption::map_orand someone forgot to adapt it for Result.