]> git.bitcoin.ninja Git - rust-lightning/commit
Use native check-cfg lint in cargo beta
authorDuncan Dean <git@dunxen.dev>
Fri, 12 Jul 2024 09:23:50 +0000 (11:23 +0200)
committerDuncan Dean <git@dunxen.dev>
Fri, 12 Jul 2024 09:48:15 +0000 (11:48 +0200)
commit99aa6e27f616c96dda2b49d09bafbc0b982251e0
tree2053e6a6ab879f8efab4b8a1513c9a66a1551fa1
parent78c0eaae55904ea0374bf2809e4cbe42b42f81b0
Use native check-cfg lint in cargo beta

This uses the newly introduced conditional configuration checks that are
now configurable withint Cargo (beta).

This allows us to get rid of our custom python script that checks for
expected features and cfgs.

This does introduce a warning regarding the unknown lint in Cargo
versions prior to the current beta, but since these are not rustc errors,
they won't break any builds with the "-D warnings" RUSTFLAG.

Moving to this lint actually exposed the "strict" feature not being
present in the lightning-invoice crate, as our python script didnt
correctly parse the cfg_attr where it appeared.
13 files changed:
.github/workflows/build.yml
Cargo.toml
ci/check-cfg-flags.py [deleted file]
lightning-background-processor/Cargo.toml
lightning-block-sync/Cargo.toml
lightning-custom-message/Cargo.toml
lightning-invoice/Cargo.toml
lightning-net-tokio/Cargo.toml
lightning-persister/Cargo.toml
lightning-rapid-gossip-sync/Cargo.toml
lightning-transaction-sync/Cargo.toml
lightning/Cargo.toml
possiblyrandom/Cargo.toml