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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API: Include the lint crate in the lint identifier #288
API: Include the lint crate in the lint identifier #288
Changes from all commits
326c9f7
18eb84d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a painful papercut. I don't fully understand how it works. Why is this
marker_lints_uitests
and not justmarker_lints
? The namemarker_lints_uitests
isn't mentioned anywhere else in this PR. I also don't see this code setup formarker_uilints
.Could this be avoided? Otherwise, could the workaround be encapsulated inside of
marker_uitest::simple_ui_test_config
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ui_test
doesn't use Cargo and instead calls the rustc driver directly. This is for a few reasons, as Cargo would need a workspace,Cargo.toml
file and would also be a bit slower for only compiling a single file. However, this also means that any environment values usually set by Cargo (starting withCARGO_*
) are not set when the uitest files are compiled.This should really only be noticed, if someone writes lints for the
marker_api::declare_lint!
macro. That's why only the uitest ofmarker_lints
required this environment value to be set. So I don't really see it as a paper cut.