Repository navigation
Tracking Issue for -Z remap-cwd-prefix #89434
Copy link
Copy link
Open
Labels
A-CLIArea: Command-line interface (CLI) to the compilerArea: Command-line interface (CLI) to the compilerA-path-remappingArea: path remapping, --remap-path-prefix, --remap-cwd-prefix, --remap-diagnostics-scope etc.Area: path remapping, --remap-path-prefix, --remap-cwd-prefix, --remap-diagnostics-scope etc.A-reproducibilityArea: Reproducible / deterministic buildsArea: Reproducible / deterministic buildsC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-needs-summaryStatus: It's hard to tell what's been done and what hasn't! Someone should do some investigation.Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Description
Activity
- addedT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCA-reproducibilityArea: Reproducible / deterministic buildsArea: Reproducible / deterministic builds
on Oct 1, 2021 -Zremap-cwd-prefix=.has been working well for me. We no longer see build environment paths in thestringsof the resulting crates and executables.When will this go to stable flags?
Reacted by Pierre Fenoll and Eliza Zhang- addedA-CLIArea: Command-line interface (CLI) to the compilerArea: Command-line interface (CLI) to the compiler
on Mar 5, 2023 - addedA-path-remappingArea: path remapping, --remap-path-prefix, --remap-cwd-prefix, --remap-diagnostics-scope etc.Area: path remapping, --remap-path-prefix, --remap-cwd-prefix, --remap-diagnostics-scope etc.S-tracking-needs-summaryStatus: It's hard to tell what's been done and what hasn't! Someone should do some investigation.Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation.
on Mar 23, 2025 - added a commit that references this issue
on Jun 13, 2026 - added a commit that references this issue
on Jun 13, 2026
Metadata
Metadata
Assignees
Labels
A-CLIArea: Command-line interface (CLI) to the compilerArea: Command-line interface (CLI) to the compilerA-path-remappingArea: path remapping, --remap-path-prefix, --remap-cwd-prefix, --remap-diagnostics-scope etc.Area: path remapping, --remap-path-prefix, --remap-cwd-prefix, --remap-diagnostics-scope etc.A-reproducibilityArea: Reproducible / deterministic buildsArea: Reproducible / deterministic buildsC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-needs-summaryStatus: It's hard to tell what's been done and what hasn't! Someone should do some investigation.Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
This is a tracking issue for
-Z remap-cwd-prefixwhich rewrites absolute paths in the current directory to the given value.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.
Unresolved Questions
--remap-path-prefix=$(pwd)=VALUE? That is, what gets remapped? Debug info, backtraces, compiler macros, coverage data, etc? What will happen if RFC 3127 results in separate mapping flags?--remap-path-scope?Implementation history