-
Notifications
You must be signed in to change notification settings - Fork 807
Whitelist cfg attrs and bump nightly version #2785
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
Conversation
Pull Request Test Coverage Report for Build 9192394789Details
💛 - Coveralls |
e3b7833
to
9e7ac4e
Compare
@@ -79,3 +79,6 @@ required-features = ["std", "rand-std", "bitcoinconsensus"] | |||
|
|||
[[example]] | |||
name = "sighash" | |||
|
|||
[lints.rust] | |||
unexpected_cfgs = { level = "deny", check-cfg = ['cfg(bench)', 'cfg(fuzzing)', 'cfg(kani)', 'cfg(mutate)', 'cfg(rust_v_1_60)'] } |
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.
rust_v_1_60
Shouldn't this be set in your build.rs
where the cfg is defined?
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.
@epage not a bad idea -- but I kinda like having everything defined here because I can easily pull stuff out of TOML files, and not-so-easily pull stuff out of .rs files, in case I want to generate a summary of all the cfg
options or do some CI sanity-checks on them or something.
units/Cargo.toml
Outdated
@@ -29,3 +29,6 @@ serde = { version = "1.0.103", default-features = false, features = ["derive"], | |||
[dev-dependencies] | |||
serde_test = "1.0" | |||
serde_json = "1.0" | |||
|
|||
[lints.rust] | |||
unexpected_cfgs = { level = "warn", check-cfg = ['cfg(kani)'] } |
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.
Just out of interest, why is this level = "warn" and the others are level = "deny"?
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.
They should all be deny
. I think I just messed one up.
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.
Sweet, review for the win.
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.
Fixed.
9e7ac4e
to
30a4825
Compare
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.
ACK 30a4825
In rust-bitcoin#2785 I modified fuzz/Cargo.toml without updating the Cargo.toml generating script. Oops. Fix that.
As we did in rust-bitcoin/rust-bitcoin#2785. rust-lang/rust#124800 has been fixed and we can update our nightly version by whitelisting all cfgs that are used.
d99b256 Remove explicit borrow (Tobin C. Harding) 7965e72 Fix rustdoc lint warnings (Tobin C. Harding) e75e7f4 Remove deprecated legacy numeric methods (Divyansh Gupta) 87e353b Update nightly version (Tobin C. Harding) 753972d cargo: whitelist all cfgs used in this repo (Andrew Poelstra) 62eca12 crypto: enable and fix accidentally disabled unit test (Andrew Poelstra) Pull request description: Backport a bunch of patches to get the clippy job passing. - the first two patches from #2785 - Update `nightly-toolchain` - the single patch from #2667 After rebase I just manually fixed all remaining lint warnings/errors ACKs for top commit: apoelstra: ACK d99b256 successfully ran local tests; nice! especially updating the rust-nightly version, which probably was not strictly necessary. will one-ack merge Tree-SHA512: 895807dc9402f88f7d2207799c50ab96841eaeb6ee1aaf8cd1a735365cc9728025c80c8c9fae0d28d4c8de6d3685121b162225a63ea64e72b749d9960a28f10e
rust-lang/rust#124800 has been fixed and we can update our nightly version by whitelisting all cfgs that are used.
There was one place where we had an old
cfg(feature = "no-std")
despite having removed the feature. By removing that cfg check we re-enabled a previously disabled test.