move lintcheck into its own crate #6884
Merged
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
This will terminate the program if run via "cargo run". "cargo run" does currently not work because at least a bunch of paths do not take that into account.
… deps would sneak in absolute paths to registry sources. make the path a relative path that starts at the CARGO_HOME to not print the users home location in the log
also hook lintcheck into clippy-dev so that `clippy dev fmt` formats it.
|
r? @Manishearth (rust-highfive has picked a reviewer for you, use r? to override) |
rust-highfive
added
the
S-waiting-on-review
|
@bors r+ |
|
📌 Commit 0af90fd has been approved by |
|
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
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.
This pr:
clippy devand into its own crate (lintcheck) (I should have done this earlier :D)cargo runin the crate root)$HOMEwhen a lint messages comes from a proc macro that originates from a crate inside the$CARGO_CACHEREADME.mdand mentions lintcheck indocs/basics.mdchangelog: none