Enhance --trim-path-prefix to also trim paths in report messages #4527
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gamesh411
force-pushed
the
trim-path-prefix-in-messages
branch
7 times, most recently
from
29c0406 to
7f296fd
Compare
gamesh411
force-pushed
the
trim-path-prefix-in-messages
branch
from
7f296fd to
f8f4f92
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The clang-diagnostic-implicit-int-conversion clang warning mentions absolute file system paths to refer to unnamed enums with source locations.
The feature --trim-path-prefix also seems aligned with the feature of removing this path prefix from the diagnostic messages.