-
Notifications
You must be signed in to change notification settings - Fork 22
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
Passing arguments to underlying invocations of cargo #1170
Comments
Might this work?
The arguments after |
That worked! Thanks! |
A follow-up on the previous question: is it possible to do the same thing with |
Hmm. For example, here it used to pass the dylint/examples/general/abs_home_path/src/lib.rs Lines 155 to 160 in 39c6cd9
So if one could figure out what flags Cargo passes to At least, I think that should work. |
Thanks again! Unfortunately, it was more complicated than just passing flags to |
Thanks, I was curious to know how this went. Can I ask what more was required? |
From what I could gather, it would require manually resolving |
On the other note, I opened this issue in |
Thanks for the explanation. It is unfortunate that |
I wonder if it is possible to run dylint lint pass with
-Z build-std
passed to all underlying cargo invocations. One of the lints I am writing depends on having standard library MIR accessible during the compilation. While it is possible to achieve this by configuring the crate on which the lint runs, it would be ideal to have this behavior out of the box for the end user.The text was updated successfully, but these errors were encountered: