-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
rustdoc: remove macro redirects #35705
Comments
Personally I don't see much reason to ever remove the redirects. For example I would expect https://doc.rust-lang.org/std/macro.assert!.html to continue to work basically forever, |
Nominating for discussion. It's been almost two years; I think we should consider this issue again. |
@rust-lang/rustdoc, what do you think? I personally don't see the harm in keeping it. Do we have crates with many more macros than the standard library, where having these redirect pages is a problem? I'm with @ollie27, keeping the link alive is more important to me than removing these small files from the output. |
I don't know why it'd cause issues so ok for me. |
Based on the rousing discussion here, I think the consensus can be described as "it's okay to keep them around". Before i close this issue, though, we should remove the FIXME that it refers to: rust/src/librustdoc/html/render.rs Lines 1969 to 1978 in 12ed235
Just to keep things neat. |
Based on the discussion in rust-lang#35705, the rustdoc team has determined that macro redirects are here to stay. Closes rust-lang#35705
A PR to remove that comment is live at #52510. |
… r=nrc rustdoc: remove FIXME about macro redirects Based on the discussion in rust-lang#35705, the rustdoc team has determined that macro redirects are here to stay. Closes rust-lang#35705
PR #35234 changed macro URLs to remove the
!
. It left redirects in so as not to break existing URLs. At some point, we should remove these redirects so as not to accumulate too much cruft. Obviously this will require some message before we do so.See FIXME in render.rs
The text was updated successfully, but these errors were encountered: