-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rollup of 10 pull requests #75865
Rollup of 10 pull requests #75865
Conversation
Also: * Fix typo in module docs * Link to `std::io::stderr` instead of `std::io::Stderr` to match the link text * Link to `std::io::stdout`
…eless_format, clippy:::for_kv_map
…r=jyn514 Use intra-doc-links in `core::{char, macros, fmt}` Helps with rust-lang#75080. r? @jyn514
…ros, r=jyn514 Switch to intra-doc links in `std::macros` Part of rust-lang#75080. --- * Switch to intra-doc links in `std::macros` * Fix typo in module docs * Link to `std::io::stderr` instead of `std::io::Stderr` to match the link text * Link to `std::io::stdout` --- @rustbot modify labels: A-intra-doc-links T-doc T-rustdoc
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!
…ation_for_derived_Ord_PartialOrd, r=KodrAus Corrected Misleading documentation for derived Ord/PartialOrd implementation Corrected Misleading documentation for derived Ord/PartialOrd implementation Fixes rust-lang#75620
doc: Prefer https link for wikipedia URLs A tiny changes.
…r=Mark-Simulacrum publish-toolstate: show more context on HTTP error The default display for HTTPError in Python does not include the request body. For GitHub API, the body includes more details about the error (like rate limiting). This could help diagnosing errors like this: rust-lang#75815 (comment)
Switch to intra-doc links in `std::collections` Part of rust-lang#75080. @rustbot modify labels: A-intra-doc-links T-doc T-rustdoc
Switch to intra-doc links in `core::array` Part of rust-lang#75080. @rustbot modify labels: A-intra-doc-links T-doc T-rustdoc
more tool clippy fixes r? @Dylan-DPC
doc: Fix typo in std::process::Child documentation Nearly done reading stdlib docs, found another small typo, here's a PR! r? @steveklabnik
📌 Commit 47a03d9 has been approved by |
bors started testing #75817 (comment) first ... is there a way to override that? That PR should really be a in rollup. |
I skipped it manually as it already started 30 min. ago. I think it shouldn't be a problem since this covers almost items in the queue and GHA is fast. |
☀️ Test successful - checks-actions, checks-azure |
Successful merges:
core::{char, macros, fmt}
#75819 (Use intra-doc-links incore::{char, macros, fmt}
)std::macros
#75821 (Switch to intra-doc links instd::macros
)std::collections
#75847 (Switch to intra-doc links instd::collections
)core::array
#75851 (Switch to intra-doc links incore::array
)Failed merges:
r? @ghost