Repository navigation
Tracking Issue for --remap-path-scope in rustdoc #155451
Description
Activity
- added a commit that references this issue
on May 21, 2026 - added a commit that references this issue
on May 21, 2026 - added a commit that references this issue
on May 28, 2026 - added a commit that references this issue
on May 30, 2026 - added a commit that references this issue
on Jun 7, 2026 - added a commit that references this issue
on Jun 8, 2026 - added a commit that references this issue
on Jun 30, 2026 - added a commit that references this issue
on Aug 7, 2026 - added 5 commits that reference this issue
on Aug 20, 2026 - added a commit that references this issue
on Aug 21, 2026 - added a commit that references this issue
on Aug 22, 2026 This RFC will appear in the Call for Testing section of the next issue (rust-lang/cargo#666) of This Week in Rust (TWiR).
You may remove the call-for-testing label. Please feel free to leave the call-for-testing label in place if you would like this RFC to appear again in another issue of TWiR.
This is a tracking issue for
--remap-path-scopein rustdoc.About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Steps
--remap-path-scopeas unstable in rustdoc #155357--remap-path-scopein rustdoc and thedocumentationscope #163895Unresolved Questions
none at this time
Implementation history
--remap-path-scopeas unstable in rustdoc #155357rustcinvocation for doctests #163956