Fix typo in documentation of i32 wrapping_abs()#75825
Merged
bors merged 1 commit intorust-lang:masterfrom Aug 24, 2020
Merged
Conversation
Contributor
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @withoutboats (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. |
rust-highfive
added
the
S-waiting-on-review
steveklabnik
approved these changes
Aug 23, 2020
Contributor
|
Thank you! @bors: r+ rollup |
Collaborator
|
📌 Commit 69d3334 has been approved by |
bors
added
S-waiting-on-bors
JohnTitor
added a commit
to JohnTitor/rust
that referenced
this pull request
Aug 24, 2020
Fix typo in documentation of i32 wrapping_abs() Hi! I was reading through the std library docs and noticed that this section flowed a bit oddly; comparing it against https://doc.rust-lang.org/std/primitive.i32.html#method.wrapping_div and https://doc.rust-lang.org/std/primitive.i32.html#method.wrapping_neg , I noticed that those two pieces of documentation used a semicolon here. This is my first time submitting a PR to this repo. Am I doing this right? Are tiny typo-fix PRs like this worth submitting, or are they not a good use of time? Thank you!
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Aug 24, 2020
Rollup of 10 pull requests Successful merges: - rust-lang#75819 (Use intra-doc-links in `core::{char, macros, fmt}`) - rust-lang#75821 (Switch to intra-doc links in `std::macros`) - rust-lang#75825 (Fix typo in documentation of i32 wrapping_abs()) - rust-lang#75826 (Corrected Misleading documentation for derived Ord/PartialOrd implementation ) - rust-lang#75831 (doc: Prefer https link for wikipedia URLs) - rust-lang#75844 (publish-toolstate: show more context on HTTP error) - rust-lang#75847 (Switch to intra-doc links in `std::collections`) - rust-lang#75851 (Switch to intra-doc links in `core::array`) - rust-lang#75856 (more tool clippy fixes) - rust-lang#75859 (doc: Fix typo in std::process::Child documentation) Failed merges: r? @ghost
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi!
I was reading through the std library docs and noticed that this section flowed a bit oddly; comparing it against https://doc.rust-lang.org/std/primitive.i32.html#method.wrapping_div and https://doc.rust-lang.org/std/primitive.i32.html#method.wrapping_neg , I noticed that those two pieces of documentation used a semicolon here.
This is my first time submitting a PR to this repo. Am I doing this right? Are tiny typo-fix PRs like this worth submitting, or are they not a good use of time?
Thank you!