-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Use more intra-doc-links in core::fmt
#75853
Conversation
☔ The latest upstream changes (presumably #73819) made this pull request unmergeable. Please resolve the merge conflicts. |
This can be merged once you rebase :) assuming that |
7711caf
to
af39af7
Compare
triage: Is this still blocked? |
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.
It seems like all of these are auto-imported, which might resolve the blockage?
@@ -102,7 +102,7 @@ pub struct Error; | |||
/// library. The [`write!`] macro accepts an instance of [`io::Write`], and the | |||
/// [`io::Write`] trait is favored over implementing this trait. | |||
/// | |||
/// [`write!`]: ../../std/macro.write.html | |||
/// [`write!`]: crate::write! |
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.
Isn't this auto-imported?
/// [`write!`]: crate::write! |
@@ -1058,7 +1058,7 @@ pub trait UpperExp { | |||
/// assert_eq!(output, "Hello world!"); | |||
/// ``` | |||
/// | |||
/// [`write!`]: ../../std/macro.write.html | |||
/// [`write!`]: crate::write! |
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.
Same here.
/// [`write!`]: crate::write! |
/// [`format_args!`]: crate::format_args | ||
/// |
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.
This too:
/// [`format_args!`]: crate::format_args | |
/// |
This should be ready to go after a rebase :) |
af39af7
to
17d3c0a
Compare
Rebased |
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.
It works 🎉
@bors r+ rollup |
📌 Commit 17d3c0a has been approved by |
Aren't all these links unnecessary though, since they're in the prelude? |
Sure, we can fix them in a follow-up. I mostly want to finally get this merged 😆 |
Rollup of 11 pull requests Successful merges: - rust-lang#75853 (Use more intra-doc-links in `core::fmt`) - rust-lang#75928 (Remove trait_selection error message in specific case) - rust-lang#76329 (Add check for doc alias attribute at crate level) - rust-lang#77219 (core::global_allocator docs link to std::alloc::GlobalAlloc) - rust-lang#77395 (BTreeMap: admit the existence of leaf edges in comments) - rust-lang#77407 (Improve build-manifest to work with the improved promote-release) - rust-lang#77426 (Include scope id in SocketAddrV6::Display) - rust-lang#77439 (Fix missing diagnostic span for `impl Trait` with const generics, and add various tests for `min_const_generics` and `const_generics`) - rust-lang#77471 (BTreeMap: refactoring around edges, missed spots) - rust-lang#77512 (Allow `Abort` terminators in all const-contexts) - rust-lang#77514 (Replace some once(x).chain(once(y)) with [x, y] IntoIter) Failed merges: r? `@ghost`
This is a follow-up to #75819, which encountered some broken links due to #75176, so this PR contains the links that are blocked on #75176.
r? @jyn514