-
Notifications
You must be signed in to change notification settings - Fork 30
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
Option to suppress unused variable warnings #6
Comments
Does it help if you use
|
Earlier today They also helped me solve the problem, and it turned out to be easier than I thought. I had the following file: # build_info.rs
#![allow(unused_variables)]
include!(concat!(env!("OUT_DIR"), "/built.rs")); However it still produced errors, and it blamed the errors on # build_info.rs
#![allow(dead_code)]
include!(concat!(env!("OUT_DIR"), "/built.rs")); With that understanding, I'm completely fine with the way things work now. If anything I'd suggest a note in the documentation. |
I'm closing this for now, please re-open is this is still a problem |
I'm using built to get a few values, but even with the options tweaked to where I want them, I still get a lot of unused const warnings. (Especially when using
Options{ env: true }
...)I'd appreciate it if there were an option to enable
allow(unused_variables)
without having to edit the file manually inbuild.rs
.I want to keep warnings enabled for my code, and most warnings for library code as well. But I'm well aware that I'm not using
NUM_JOBS
, I don't need to see that every time I build.The text was updated successfully, but these errors were encountered: