Strip cargo lints table #13806
Closed
Strip cargo lints table #13806
Conversation
This file contains 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
|
r? @weihanglo rustbot has assigned @weihanglo. Use |
rustbot
added
A-manifest
|
I was wondering if we should just completely strip the table on publish. This got me thinking, is there a downside to doing it completely? If so, is there a downside to doing it here? Maybe if If we wanted to include it, we could make it based on your |
|
☔ The latest upstream changes (presumably #13713) made this pull request unmergeable. Please resolve the merge conflicts. |
|
#13833 supersedes this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
[lints.cargo]should be removed when publishing/packaging to avoid unintentional MSRV bumps, and this PR makes it so the table is removed.