[INFO] fetching crate bv 0.11.1...
[INFO] testing bv-0.11.1 against try#8de4c7234dd9b97c9d76b58671343fdbbc9a433e+target=x86_64-unknown-linux-musl for musl_upgrade_1_2_5_with_libc_patch_0
[INFO] extracting crate bv 0.11.1 into /workspace/builds/worker-1-tc1/source
[INFO] started tweaking crates.io crate bv 0.11.1
[INFO] finished tweaking crates.io crate bv 0.11.1
[INFO] tweaked toml for crates.io crate bv 0.11.1 written to /workspace/builds/worker-1-tc1/source/Cargo.toml
[INFO] validating manifest of crates.io crate bv 0.11.1 on toolchain 8de4c7234dd9b97c9d76b58671343fdbbc9a433e
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 40 packages to latest compatible versions
[INFO] [stderr]       Adding quickcheck v0.6.2 (available: v1.0.3)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 38aa3eea9a42410f5ad05b1fd1ef8b104efbb6f9303ecdff95f564768161d434
[INFO] running `Command { std: "docker" "start" "-a" "38aa3eea9a42410f5ad05b1fd1ef8b104efbb6f9303ecdff95f564768161d434", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "38aa3eea9a42410f5ad05b1fd1ef8b104efbb6f9303ecdff95f564768161d434", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "38aa3eea9a42410f5ad05b1fd1ef8b104efbb6f9303ecdff95f564768161d434", kill_on_drop: false }`
[INFO] [stdout] 38aa3eea9a42410f5ad05b1fd1ef8b104efbb6f9303ecdff95f564768161d434
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "build" "--frozen" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }`
[INFO] [stdout] 18a975a239444899c6648abbf1d8959bc67502ff5694f7434a0e50d2f8d4ce88
[INFO] running `Command { std: "docker" "start" "-a" "18a975a239444899c6648abbf1d8959bc67502ff5694f7434a0e50d2f8d4ce88", kill_on_drop: false }`
[INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024
[INFO] [stderr]    Compiling feature-probe v0.1.1
[INFO] [stderr]    Compiling bv v0.11.1 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]  --> src/range_compat.rs:3:7
[INFO] [stdout]   |
[INFO] [stdout] 3 | #[cfg(inclusive_range)]
[INFO] [stdout]   |       ^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stdout]   = help: consider using a Cargo feature instead
[INFO] [stdout]   = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]            [lints.rust]
[INFO] [stdout]            unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]   = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]  --> src/range_compat.rs:6:7
[INFO] [stdout]   |
[INFO] [stdout] 6 | #[cfg(inclusive_range)]
[INFO] [stdout]   |       ^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = help: consider using a Cargo feature instead
[INFO] [stdout]   = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]            [lints.rust]
[INFO] [stdout]            unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]   = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `int_128`
[INFO] [stdout]    --> src/storage.rs:330:7
[INFO] [stdout]     |
[INFO] [stdout] 330 | #[cfg(int_128)]
[INFO] [stdout]     |       ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(int_128)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(int_128)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]   --> src/traits/bit_sliceable.rs:90:7
[INFO] [stdout]    |
[INFO] [stdout] 90 | #[cfg(inclusive_range)]
[INFO] [stdout]    |       ^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/traits/bit_sliceable.rs:104:7
[INFO] [stdout]     |
[INFO] [stdout] 104 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/traits/bit_sliceable.rs:147:7
[INFO] [stdout]     |
[INFO] [stdout] 147 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/traits/bit_sliceable.rs:156:7
[INFO] [stdout]     |
[INFO] [stdout] 156 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/slice.rs:487:7
[INFO] [stdout]     |
[INFO] [stdout] 487 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/slice.rs:504:7
[INFO] [stdout]     |
[INFO] [stdout] 504 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/slice.rs:555:7
[INFO] [stdout]     |
[INFO] [stdout] 555 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/slice.rs:564:7
[INFO] [stdout]     |
[INFO] [stdout] 564 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unnecessary parentheses around block return value
[INFO] [stdout]    --> src/slice.rs:112:17
[INFO] [stdout]     |
[INFO] [stdout] 112 |                 (chunk1 | (chunk2 << shift2))
[INFO] [stdout]     |                 ^                           ^
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_parens)]` on by default
[INFO] [stdout] help: remove these parentheses
[INFO] [stdout]     |
[INFO] [stdout] 112 -                 (chunk1 | (chunk2 << shift2))
[INFO] [stdout] 112 +                 chunk1 | (chunk2 << shift2)
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/bit_vec/impls.rs:121:7
[INFO] [stdout]     |
[INFO] [stdout] 121 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/bit_vec/impls.rs:130:7
[INFO] [stdout]     |
[INFO] [stdout] 130 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/bit_vec/impls.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/bit_vec/impls.rs:180:7
[INFO] [stdout]     |
[INFO] [stdout] 180 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `int_128`
[INFO] [stdout]   --> src/prims.rs:70:7
[INFO] [stdout]    |
[INFO] [stdout] 70 | #[cfg(int_128)]
[INFO] [stdout]    |       ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(int_128)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(int_128)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:252:7
[INFO] [stdout]     |
[INFO] [stdout] 252 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:263:7
[INFO] [stdout]     |
[INFO] [stdout] 263 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:309:7
[INFO] [stdout]     |
[INFO] [stdout] 309 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:320:7
[INFO] [stdout]     |
[INFO] [stdout] 320 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unnecessary parentheses around block return value
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:205:9
[INFO] [stdout]     |
[INFO] [stdout] 205 |         (start + len - real_start)
[INFO] [stdout]     |         ^                        ^
[INFO] [stdout]     |
[INFO] [stdout] help: remove these parentheses
[INFO] [stdout]     |
[INFO] [stdout] 205 -         (start + len - real_start)
[INFO] [stdout] 205 +         start + len - real_start
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:145:1
[INFO] [stdout]     |
[INFO] [stdout] 145 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 146 | |     impl['a, T: Bits] BitSliceable for &'a BitNot<T>;
[INFO] [stdout] 147 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:145:1
[INFO] [stdout]     |
[INFO] [stdout] 145 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 146 | |     impl['a, T: Bits] BitSliceable for &'a BitNot<T>;
[INFO] [stdout] 147 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:221:1
[INFO] [stdout]     |
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:221:1
[INFO] [stdout]     |
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:222:1
[INFO] [stdout]     |
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:222:1
[INFO] [stdout]     |
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:223:1
[INFO] [stdout]     |
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:223:1
[INFO] [stdout]     |
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:269:1
[INFO] [stdout]     |
[INFO] [stdout] 269 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 270 | |     impl['a, T: Bits, U: Bits<Block = T::Block>,
[INFO] [stdout] 271 | |          F: Fn(T::Block, T::Block) -> T::Block]
[INFO] [stdout] 272 | |         BitSliceable for &'a BitZip<T, U, F>;
[INFO] [stdout] 273 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:269:1
[INFO] [stdout]     |
[INFO] [stdout] 269 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 270 | |     impl['a, T: Bits, U: Bits<Block = T::Block>,
[INFO] [stdout] 271 | |          F: Fn(T::Block, T::Block) -> T::Block]
[INFO] [stdout] 272 | |         BitSliceable for &'a BitZip<T, U, F>;
[INFO] [stdout] 273 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/bit_fill.rs:74:1
[INFO] [stdout]     |
[INFO] [stdout] 74  | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 75  | |     impl[Block: BlockType] BitSliceable for BitFill<Block>;
[INFO] [stdout] 76  | |     impl['a, Block: BlockType] BitSliceable for &'a BitFill<Block>;
[INFO] [stdout] 77  | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/bit_fill.rs:74:1
[INFO] [stdout]     |
[INFO] [stdout] 74  | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 75  | |     impl[Block: BlockType] BitSliceable for BitFill<Block>;
[INFO] [stdout] 76  | |     impl['a, Block: BlockType] BitSliceable for &'a BitFill<Block>;
[INFO] [stdout] 77  | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/bit_concat.rs:73:1
[INFO] [stdout]     |
[INFO] [stdout] 73  | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 74  | |     impl[T: Bits, U: Bits<Block = T::Block>] BitSliceable for BitConcat<T, U>;
[INFO] [stdout] 75  | |     impl['a, T: Bits, U: Bits<Block = T::Block>] BitSliceable for &'a BitConcat<T, U>;
[INFO] [stdout] 76  | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/bit_concat.rs:73:1
[INFO] [stdout]     |
[INFO] [stdout] 73  | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 74  | |     impl[T: Bits, U: Bits<Block = T::Block>] BitSliceable for BitConcat<T, U>;
[INFO] [stdout] 75  | |     impl['a, T: Bits, U: Bits<Block = T::Block>] BitSliceable for &'a BitConcat<T, U>;
[INFO] [stdout] 76  | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]   --> src/traits/bits.rs:62:17
[INFO] [stdout]    |
[INFO] [stdout] 62 | /                 format!("Bits::get_block: out of bounds ({}/{})",
[INFO] [stdout] 63 | |                         position, self.block_len()));
[INFO] [stdout]    | |___________________________________________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]    = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]    = note: `#[warn(non_fmt_panics)]` on by default
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]    |
[INFO] [stdout] 62 ~                 "Bits::get_block: out of bounds ({}/{})",
[INFO] [stdout] 63 ~                         position, self.block_len());
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/bit_vec/mod.rs:497:21
[INFO] [stdout]     |
[INFO] [stdout] 497 |     pub fn as_slice(&self) -> BitSlice<Block> {
[INFO] [stdout]     |                     ^^^^^     --------------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 497 |     pub fn as_slice(&self) -> BitSlice<'_, Block> {
[INFO] [stdout]     |                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/bit_vec/mod.rs:523:25
[INFO] [stdout]     |
[INFO] [stdout] 523 |     pub fn as_mut_slice(&mut self) -> BitSliceMut<Block> {
[INFO] [stdout]     |                         ^^^^^^^^^     ------------------ the lifetime gets resolved as `'_`
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 523 |     pub fn as_mut_slice(&mut self) -> BitSliceMut<'_, Block> {
[INFO] [stdout]     |                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:145:1
[INFO] [stdout]     |
[INFO] [stdout] 145 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 146 | |     impl['a, T: Bits] BitSliceable for &'a BitNot<T>;
[INFO] [stdout] 147 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:172:26
[INFO] [stdout]     |
[INFO] [stdout] 172 |                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 172 -                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout] 172 +                          "{}::get_bit: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:178:26
[INFO] [stdout]     |
[INFO] [stdout] 178 |                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 178 -                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout] 178 +                          "{}::get_block: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  | ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:221:1
[INFO] [stdout]     |
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:172:26
[INFO] [stdout]     |
[INFO] [stdout] 172 |                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 172 -                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout] 172 +                          "{}::get_bit: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:178:26
[INFO] [stdout]     |
[INFO] [stdout] 178 |                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 178 -                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout] 178 +                          "{}::get_block: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  | ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:222:1
[INFO] [stdout]     |
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:172:26
[INFO] [stdout]     |
[INFO] [stdout] 172 |                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 172 -                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout] 172 +                          "{}::get_bit: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:178:26
[INFO] [stdout]     |
[INFO] [stdout] 178 |                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 178 -                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout] 178 +                          "{}::get_block: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  | ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:223:1
[INFO] [stdout]     |
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:269:1
[INFO] [stdout]     |
[INFO] [stdout] 269 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 270 | |     impl['a, T: Bits, U: Bits<Block = T::Block>,
[INFO] [stdout] 271 | |          F: Fn(T::Block, T::Block) -> T::Block]
[INFO] [stdout] 272 | |         BitSliceable for &'a BitZip<T, U, F>;
[INFO] [stdout] 273 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]   --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]    |
[INFO] [stdout] 90 |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]    |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: src/adapter/bit_fill.rs:74:1
[INFO] [stdout]    |
[INFO] [stdout] 74 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 75 | |     impl[Block: BlockType] BitSliceable for BitFill<Block>;
[INFO] [stdout] 76 | |     impl['a, Block: BlockType] BitSliceable for &'a BitFill<Block>;
[INFO] [stdout] 77 | | }
[INFO] [stdout]    | |_- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]    = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]    = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]    |
[INFO] [stdout] 90 -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90 +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]   --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]    |
[INFO] [stdout] 90 |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]    |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: src/adapter/bit_concat.rs:73:1
[INFO] [stdout]    |
[INFO] [stdout] 73 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 74 | |     impl[T: Bits, U: Bits<Block = T::Block>] BitSliceable for BitConcat<T, U>;
[INFO] [stdout] 75 | |     impl['a, T: Bits, U: Bits<Block = T::Block>] BitSliceable for &'a BitConcat<T, U>;
[INFO] [stdout] 76 | | }
[INFO] [stdout]    | |_- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]    = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]    = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]    |
[INFO] [stdout] 90 -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90 +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.85s
[INFO] running `Command { std: "docker" "inspect" "18a975a239444899c6648abbf1d8959bc67502ff5694f7434a0e50d2f8d4ce88", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "18a975a239444899c6648abbf1d8959bc67502ff5694f7434a0e50d2f8d4ce88", kill_on_drop: false }`
[INFO] [stdout] 18a975a239444899c6648abbf1d8959bc67502ff5694f7434a0e50d2f8d4ce88
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "test" "--frozen" "--no-run" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }`
[INFO] [stdout] aef6f60c344334f80cd48095f8bf8ba14ac0770c364385c88c1515274f4ab3a2
[INFO] running `Command { std: "docker" "start" "-a" "aef6f60c344334f80cd48095f8bf8ba14ac0770c364385c88c1515274f4ab3a2", kill_on_drop: false }`
[INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]  --> src/range_compat.rs:3:7
[INFO] [stdout]   |
[INFO] [stdout] 3 | #[cfg(inclusive_range)]
[INFO] [stdout]   |       ^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stdout]   = help: consider using a Cargo feature instead
[INFO] [stdout]   = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]            [lints.rust]
[INFO] [stdout]            unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]   = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]  --> src/range_compat.rs:6:7
[INFO] [stdout]   |
[INFO] [stdout] 6 | #[cfg(inclusive_range)]
[INFO] [stdout]   |       ^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = help: consider using a Cargo feature instead
[INFO] [stdout]   = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]            [lints.rust]
[INFO] [stdout]            unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]   = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `int_128`
[INFO] [stdout]    --> src/storage.rs:330:7
[INFO] [stdout]     |
[INFO] [stdout] 330 | #[cfg(int_128)]
[INFO] [stdout]     |       ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(int_128)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(int_128)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]   --> src/traits/bit_sliceable.rs:90:7
[INFO] [stdout]    |
[INFO] [stdout] 90 | #[cfg(inclusive_range)]
[INFO] [stdout]    |       ^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/traits/bit_sliceable.rs:104:7
[INFO] [stdout]     |
[INFO] [stdout] 104 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/traits/bit_sliceable.rs:147:7
[INFO] [stdout]     |
[INFO] [stdout] 147 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/traits/bit_sliceable.rs:156:7
[INFO] [stdout]     |
[INFO] [stdout] 156 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/slice.rs:487:7
[INFO] [stdout]     |
[INFO] [stdout] 487 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/slice.rs:504:7
[INFO] [stdout]     |
[INFO] [stdout] 504 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/slice.rs:555:7
[INFO] [stdout]     |
[INFO] [stdout] 555 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/slice.rs:564:7
[INFO] [stdout]     |
[INFO] [stdout] 564 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unnecessary parentheses around block return value
[INFO] [stdout]    --> src/slice.rs:112:17
[INFO] [stdout]     |
[INFO] [stdout] 112 |                 (chunk1 | (chunk2 << shift2))
[INFO] [stdout]     |                 ^                           ^
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_parens)]` on by default
[INFO] [stdout] help: remove these parentheses
[INFO] [stdout]     |
[INFO] [stdout] 112 -                 (chunk1 | (chunk2 << shift2))
[INFO] [stdout] 112 +                 chunk1 | (chunk2 << shift2)
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/bit_vec/impls.rs:121:7
[INFO] [stdout]     |
[INFO] [stdout] 121 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/bit_vec/impls.rs:130:7
[INFO] [stdout]     |
[INFO] [stdout] 130 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/bit_vec/impls.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/bit_vec/impls.rs:180:7
[INFO] [stdout]     |
[INFO] [stdout] 180 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `int_128`
[INFO] [stdout]   --> src/prims.rs:70:7
[INFO] [stdout]    |
[INFO] [stdout] 70 | #[cfg(int_128)]
[INFO] [stdout]    |       ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(int_128)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(int_128)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:252:7
[INFO] [stdout]     |
[INFO] [stdout] 252 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:263:7
[INFO] [stdout]     |
[INFO] [stdout] 263 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:309:7
[INFO] [stdout]     |
[INFO] [stdout] 309 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:320:7
[INFO] [stdout]     |
[INFO] [stdout] 320 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unnecessary parentheses around block return value
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:205:9
[INFO] [stdout]     |
[INFO] [stdout] 205 |         (start + len - real_start)
[INFO] [stdout]     |         ^                        ^
[INFO] [stdout]     |
[INFO] [stdout] help: remove these parentheses
[INFO] [stdout]     |
[INFO] [stdout] 205 -         (start + len - real_start)
[INFO] [stdout] 205 +         start + len - real_start
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:145:1
[INFO] [stdout]     |
[INFO] [stdout] 145 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 146 | |     impl['a, T: Bits] BitSliceable for &'a BitNot<T>;
[INFO] [stdout] 147 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:145:1
[INFO] [stdout]     |
[INFO] [stdout] 145 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 146 | |     impl['a, T: Bits] BitSliceable for &'a BitNot<T>;
[INFO] [stdout] 147 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:221:1
[INFO] [stdout]     |
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:221:1
[INFO] [stdout]     |
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:222:1
[INFO] [stdout]     |
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:222:1
[INFO] [stdout]     |
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:223:1
[INFO] [stdout]     |
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:223:1
[INFO] [stdout]     |
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:269:1
[INFO] [stdout]     |
[INFO] [stdout] 269 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 270 | |     impl['a, T: Bits, U: Bits<Block = T::Block>,
[INFO] [stdout] 271 | |          F: Fn(T::Block, T::Block) -> T::Block]
[INFO] [stdout] 272 | |         BitSliceable for &'a BitZip<T, U, F>;
[INFO] [stdout] 273 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:269:1
[INFO] [stdout]     |
[INFO] [stdout] 269 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 270 | |     impl['a, T: Bits, U: Bits<Block = T::Block>,
[INFO] [stdout] 271 | |          F: Fn(T::Block, T::Block) -> T::Block]
[INFO] [stdout] 272 | |         BitSliceable for &'a BitZip<T, U, F>;
[INFO] [stdout] 273 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/bit_fill.rs:74:1
[INFO] [stdout]     |
[INFO] [stdout] 74  | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 75  | |     impl[Block: BlockType] BitSliceable for BitFill<Block>;
[INFO] [stdout] 76  | |     impl['a, Block: BlockType] BitSliceable for &'a BitFill<Block>;
[INFO] [stdout] 77  | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/bit_fill.rs:74:1
[INFO] [stdout]     |
[INFO] [stdout] 74  | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 75  | |     impl[Block: BlockType] BitSliceable for BitFill<Block>;
[INFO] [stdout] 76  | |     impl['a, Block: BlockType] BitSliceable for &'a BitFill<Block>;
[INFO] [stdout] 77  | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/bit_concat.rs:73:1
[INFO] [stdout]     |
[INFO] [stdout] 73  | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 74  | |     impl[T: Bits, U: Bits<Block = T::Block>] BitSliceable for BitConcat<T, U>;
[INFO] [stdout] 75  | |     impl['a, T: Bits, U: Bits<Block = T::Block>] BitSliceable for &'a BitConcat<T, U>;
[INFO] [stdout] 76  | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/bit_concat.rs:73:1
[INFO] [stdout]     |
[INFO] [stdout] 73  | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 74  | |     impl[T: Bits, U: Bits<Block = T::Block>] BitSliceable for BitConcat<T, U>;
[INFO] [stdout] 75  | |     impl['a, T: Bits, U: Bits<Block = T::Block>] BitSliceable for &'a BitConcat<T, U>;
[INFO] [stdout] 76  | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]   --> src/traits/bits.rs:62:17
[INFO] [stdout]    |
[INFO] [stdout] 62 | /                 format!("Bits::get_block: out of bounds ({}/{})",
[INFO] [stdout] 63 | |                         position, self.block_len()));
[INFO] [stdout]    | |___________________________________________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]    = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]    = note: `#[warn(non_fmt_panics)]` on by default
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]    |
[INFO] [stdout] 62 ~                 "Bits::get_block: out of bounds ({}/{})",
[INFO] [stdout] 63 ~                         position, self.block_len());
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/bit_vec/mod.rs:497:21
[INFO] [stdout]     |
[INFO] [stdout] 497 |     pub fn as_slice(&self) -> BitSlice<Block> {
[INFO] [stdout]     |                     ^^^^^     --------------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 497 |     pub fn as_slice(&self) -> BitSlice<'_, Block> {
[INFO] [stdout]     |                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/bit_vec/mod.rs:523:25
[INFO] [stdout]     |
[INFO] [stdout] 523 |     pub fn as_mut_slice(&mut self) -> BitSliceMut<Block> {
[INFO] [stdout]     |                         ^^^^^^^^^     ------------------ the lifetime gets resolved as `'_`
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 523 |     pub fn as_mut_slice(&mut self) -> BitSliceMut<'_, Block> {
[INFO] [stdout]     |                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:145:1
[INFO] [stdout]     |
[INFO] [stdout] 145 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 146 | |     impl['a, T: Bits] BitSliceable for &'a BitNot<T>;
[INFO] [stdout] 147 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:172:26
[INFO] [stdout]     |
[INFO] [stdout] 172 |                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 172 -                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout] 172 +                          "{}::get_bit: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:178:26
[INFO] [stdout]     |
[INFO] [stdout] 178 |                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 178 -                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout] 178 +                          "{}::get_block: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  | ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:221:1
[INFO] [stdout]     |
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:172:26
[INFO] [stdout]     |
[INFO] [stdout] 172 |                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 172 -                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout] 172 +                          "{}::get_bit: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:178:26
[INFO] [stdout]     |
[INFO] [stdout] 178 |                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 178 -                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout] 178 +                          "{}::get_block: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  | ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:222:1
[INFO] [stdout]     |
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:172:26
[INFO] [stdout]     |
[INFO] [stdout] 172 |                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 172 -                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout] 172 +                          "{}::get_bit: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:178:26
[INFO] [stdout]     |
[INFO] [stdout] 178 |                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 178 -                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout] 178 +                          "{}::get_block: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  | ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:223:1
[INFO] [stdout]     |
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:269:1
[INFO] [stdout]     |
[INFO] [stdout] 269 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 270 | |     impl['a, T: Bits, U: Bits<Block = T::Block>,
[INFO] [stdout] 271 | |          F: Fn(T::Block, T::Block) -> T::Block]
[INFO] [stdout] 272 | |         BitSliceable for &'a BitZip<T, U, F>;
[INFO] [stdout] 273 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling bv v0.11.1 (/opt/rustwide/workdir)
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]   --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]    |
[INFO] [stdout] 90 |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]    |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: src/adapter/bit_fill.rs:74:1
[INFO] [stdout]    |
[INFO] [stdout] 74 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 75 | |     impl[Block: BlockType] BitSliceable for BitFill<Block>;
[INFO] [stdout] 76 | |     impl['a, Block: BlockType] BitSliceable for &'a BitFill<Block>;
[INFO] [stdout] 77 | | }
[INFO] [stdout]    | |_- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]    = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]    = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]    |
[INFO] [stdout] 90 -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90 +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]   --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]    |
[INFO] [stdout] 90 |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]    |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: src/adapter/bit_concat.rs:73:1
[INFO] [stdout]    |
[INFO] [stdout] 73 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 74 | |     impl[T: Bits, U: Bits<Block = T::Block>] BitSliceable for BitConcat<T, U>;
[INFO] [stdout] 75 | |     impl['a, T: Bits, U: Bits<Block = T::Block>] BitSliceable for &'a BitConcat<T, U>;
[INFO] [stdout] 76 | | }
[INFO] [stdout]    | |_- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]    = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]    = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]    |
[INFO] [stdout] 90 -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90 +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]  --> src/range_compat.rs:3:7
[INFO] [stdout]   |
[INFO] [stdout] 3 | #[cfg(inclusive_range)]
[INFO] [stdout]   |       ^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stdout]   = help: consider using a Cargo feature instead
[INFO] [stdout]   = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]            [lints.rust]
[INFO] [stdout]            unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]   = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]  --> src/range_compat.rs:6:7
[INFO] [stdout]   |
[INFO] [stdout] 6 | #[cfg(inclusive_range)]
[INFO] [stdout]   |       ^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = help: consider using a Cargo feature instead
[INFO] [stdout]   = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]            [lints.rust]
[INFO] [stdout]            unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]   = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `int_128`
[INFO] [stdout]    --> src/storage.rs:330:7
[INFO] [stdout]     |
[INFO] [stdout] 330 | #[cfg(int_128)]
[INFO] [stdout]     |       ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(int_128)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(int_128)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]   --> src/traits/bit_sliceable.rs:90:7
[INFO] [stdout]    |
[INFO] [stdout] 90 | #[cfg(inclusive_range)]
[INFO] [stdout]    |       ^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/traits/bit_sliceable.rs:104:7
[INFO] [stdout]     |
[INFO] [stdout] 104 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/traits/bit_sliceable.rs:147:7
[INFO] [stdout]     |
[INFO] [stdout] 147 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/traits/bit_sliceable.rs:156:7
[INFO] [stdout]     |
[INFO] [stdout] 156 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/slice.rs:487:7
[INFO] [stdout]     |
[INFO] [stdout] 487 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/slice.rs:504:7
[INFO] [stdout]     |
[INFO] [stdout] 504 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/slice.rs:555:7
[INFO] [stdout]     |
[INFO] [stdout] 555 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/slice.rs:564:7
[INFO] [stdout]     |
[INFO] [stdout] 564 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unnecessary parentheses around block return value
[INFO] [stdout]    --> src/slice.rs:112:17
[INFO] [stdout]     |
[INFO] [stdout] 112 |                 (chunk1 | (chunk2 << shift2))
[INFO] [stdout]     |                 ^                           ^
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_parens)]` on by default
[INFO] [stdout] help: remove these parentheses
[INFO] [stdout]     |
[INFO] [stdout] 112 -                 (chunk1 | (chunk2 << shift2))
[INFO] [stdout] 112 +                 chunk1 | (chunk2 << shift2)
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/slice.rs:753:11
[INFO] [stdout]     |
[INFO] [stdout] 753 |     #[cfg(inclusive_range)]
[INFO] [stdout]     |           ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/bit_vec/impls.rs:121:7
[INFO] [stdout]     |
[INFO] [stdout] 121 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/bit_vec/impls.rs:130:7
[INFO] [stdout]     |
[INFO] [stdout] 130 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/bit_vec/impls.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/bit_vec/impls.rs:180:7
[INFO] [stdout]     |
[INFO] [stdout] 180 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `int_128`
[INFO] [stdout]   --> src/prims.rs:70:7
[INFO] [stdout]    |
[INFO] [stdout] 70 | #[cfg(int_128)]
[INFO] [stdout]    |       ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(int_128)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(int_128)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `int_128`
[INFO] [stdout]    --> src/prims.rs:134:11
[INFO] [stdout]     |
[INFO] [stdout] 134 |     #[cfg(int_128)]
[INFO] [stdout]     |           ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(int_128)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(int_128)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:252:7
[INFO] [stdout]     |
[INFO] [stdout] 252 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:263:7
[INFO] [stdout]     |
[INFO] [stdout] 263 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:309:7
[INFO] [stdout]     |
[INFO] [stdout] 309 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:320:7
[INFO] [stdout]     |
[INFO] [stdout] 320 | #[cfg(inclusive_range)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unnecessary parentheses around block return value
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:205:9
[INFO] [stdout]     |
[INFO] [stdout] 205 |         (start + len - real_start)
[INFO] [stdout]     |         ^                        ^
[INFO] [stdout]     |
[INFO] [stdout] help: remove these parentheses
[INFO] [stdout]     |
[INFO] [stdout] 205 -         (start + len - real_start)
[INFO] [stdout] 205 +         start + len - real_start
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:145:1
[INFO] [stdout]     |
[INFO] [stdout] 145 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 146 | |     impl['a, T: Bits] BitSliceable for &'a BitNot<T>;
[INFO] [stdout] 147 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:145:1
[INFO] [stdout]     |
[INFO] [stdout] 145 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 146 | |     impl['a, T: Bits] BitSliceable for &'a BitNot<T>;
[INFO] [stdout] 147 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:221:1
[INFO] [stdout]     |
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:221:1
[INFO] [stdout]     |
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:222:1
[INFO] [stdout]     |
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:222:1
[INFO] [stdout]     |
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:223:1
[INFO] [stdout]     |
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |             #[cfg(inclusive_range)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:223:1
[INFO] [stdout]     |
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:269:1
[INFO] [stdout]     |
[INFO] [stdout] 269 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 270 | |     impl['a, T: Bits, U: Bits<Block = T::Block>,
[INFO] [stdout] 271 | |          F: Fn(T::Block, T::Block) -> T::Block]
[INFO] [stdout] 272 | |         BitSliceable for &'a BitZip<T, U, F>;
[INFO] [stdout] 273 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:269:1
[INFO] [stdout]     |
[INFO] [stdout] 269 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 270 | |     impl['a, T: Bits, U: Bits<Block = T::Block>,
[INFO] [stdout] 271 | |          F: Fn(T::Block, T::Block) -> T::Block]
[INFO] [stdout] 272 | |         BitSliceable for &'a BitZip<T, U, F>;
[INFO] [stdout] 273 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/bit_fill.rs:74:1
[INFO] [stdout]     |
[INFO] [stdout] 74  | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 75  | |     impl[Block: BlockType] BitSliceable for BitFill<Block>;
[INFO] [stdout] 76  | |     impl['a, Block: BlockType] BitSliceable for &'a BitFill<Block>;
[INFO] [stdout] 77  | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/bit_fill.rs:74:1
[INFO] [stdout]     |
[INFO] [stdout] 74  | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 75  | |     impl[Block: BlockType] BitSliceable for BitFill<Block>;
[INFO] [stdout] 76  | |     impl['a, Block: BlockType] BitSliceable for &'a BitFill<Block>;
[INFO] [stdout] 77  | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stdout]     |
[INFO] [stdout] 121 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/bit_concat.rs:73:1
[INFO] [stdout]     |
[INFO] [stdout] 73  | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 74  | |     impl[T: Bits, U: Bits<Block = T::Block>] BitSliceable for BitConcat<T, U>;
[INFO] [stdout] 75  | |     impl['a, T: Bits, U: Bits<Block = T::Block>] BitSliceable for &'a BitConcat<T, U>;
[INFO] [stdout] 76  | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stdout]     |
[INFO] [stdout] 132 |               #[cfg(inclusive_range)]
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/bit_concat.rs:73:1
[INFO] [stdout]     |
[INFO] [stdout] 73  | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 74  | |     impl[T: Bits, U: Bits<Block = T::Block>] BitSliceable for BitConcat<T, U>;
[INFO] [stdout] 75  | |     impl['a, T: Bits, U: Bits<Block = T::Block>] BitSliceable for &'a BitConcat<T, U>;
[INFO] [stdout] 76  | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]   --> src/traits/bits.rs:62:17
[INFO] [stdout]    |
[INFO] [stdout] 62 | /                 format!("Bits::get_block: out of bounds ({}/{})",
[INFO] [stdout] 63 | |                         position, self.block_len()));
[INFO] [stdout]    | |___________________________________________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]    = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]    = note: `#[warn(non_fmt_panics)]` on by default
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]    |
[INFO] [stdout] 62 ~                 "Bits::get_block: out of bounds ({}/{})",
[INFO] [stdout] 63 ~                         position, self.block_len());
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/bit_vec/mod.rs:497:21
[INFO] [stdout]     |
[INFO] [stdout] 497 |     pub fn as_slice(&self) -> BitSlice<Block> {
[INFO] [stdout]     |                     ^^^^^     --------------- the lifetime gets resolved as `'_`
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 497 |     pub fn as_slice(&self) -> BitSlice<'_, Block> {
[INFO] [stdout]     |                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stdout]    --> src/bit_vec/mod.rs:523:25
[INFO] [stdout]     |
[INFO] [stdout] 523 |     pub fn as_mut_slice(&mut self) -> BitSliceMut<Block> {
[INFO] [stdout]     |                         ^^^^^^^^^     ------------------ the lifetime gets resolved as `'_`
[INFO] [stdout]     |                         |
[INFO] [stdout]     |                         this lifetime flows to the output
[INFO] [stdout]     |
[INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stdout]     |
[INFO] [stdout] 523 |     pub fn as_mut_slice(&mut self) -> BitSliceMut<'_, Block> {
[INFO] [stdout]     |                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:145:1
[INFO] [stdout]     |
[INFO] [stdout] 145 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 146 | |     impl['a, T: Bits] BitSliceable for &'a BitNot<T>;
[INFO] [stdout] 147 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:172:26
[INFO] [stdout]     |
[INFO] [stdout] 172 |                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 172 -                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout] 172 +                          "{}::get_bit: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:178:26
[INFO] [stdout]     |
[INFO] [stdout] 178 |                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 178 -                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout] 178 +                          "{}::get_block: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  | ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:221:1
[INFO] [stdout]     |
[INFO] [stdout] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:172:26
[INFO] [stdout]     |
[INFO] [stdout] 172 |                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 172 -                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout] 172 +                          "{}::get_bit: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:178:26
[INFO] [stdout]     |
[INFO] [stdout] 178 |                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 178 -                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout] 178 +                          "{}::get_block: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  | ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:222:1
[INFO] [stdout]     |
[INFO] [stdout] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:172:26
[INFO] [stdout]     |
[INFO] [stdout] 172 |                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 172 -                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stdout] 172 +                          "{}::get_bit: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/logic.rs:178:26
[INFO] [stdout]     |
[INFO] [stdout] 178 |                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 178 -                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stdout] 178 +                          "{}::get_block: out of bounds", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  | ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:223:1
[INFO] [stdout]     |
[INFO] [stdout] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]     |
[INFO] [stdout] 90  |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    ::: src/adapter/logic.rs:269:1
[INFO] [stdout]     |
[INFO] [stdout] 269 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 270 | |     impl['a, T: Bits, U: Bits<Block = T::Block>,
[INFO] [stdout] 271 | |          F: Fn(T::Block, T::Block) -> T::Block]
[INFO] [stdout] 272 | |         BitSliceable for &'a BitZip<T, U, F>;
[INFO] [stdout] 273 | | }
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]     |
[INFO] [stdout] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]   --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]    |
[INFO] [stdout] 90 |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]    |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: src/adapter/bit_fill.rs:74:1
[INFO] [stdout]    |
[INFO] [stdout] 74 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 75 | |     impl[Block: BlockType] BitSliceable for BitFill<Block>;
[INFO] [stdout] 76 | |     impl['a, Block: BlockType] BitSliceable for &'a BitFill<Block>;
[INFO] [stdout] 77 | | }
[INFO] [stdout]    | |_- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]    = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]    = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]    |
[INFO] [stdout] 90 -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90 +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: panic message is not a string literal
[INFO] [stdout]   --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stdout]    |
[INFO] [stdout] 90 |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout]    |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: src/adapter/bit_concat.rs:73:1
[INFO] [stdout]    |
[INFO] [stdout] 73 | / impl_bit_sliceable_adapter! {
[INFO] [stdout] 74 | |     impl[T: Bits, U: Bits<Block = T::Block>] BitSliceable for BitConcat<T, U>;
[INFO] [stdout] 75 | |     impl['a, T: Bits, U: Bits<Block = T::Block>] BitSliceable for &'a BitConcat<T, U>;
[INFO] [stdout] 76 | | }
[INFO] [stdout]    | |_- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stdout]    = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stdout]    = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: remove the `format!(..)` macro call
[INFO] [stdout]    |
[INFO] [stdout] 90 -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stdout] 90 +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 4.27s
[INFO] running `Command { std: "docker" "inspect" "aef6f60c344334f80cd48095f8bf8ba14ac0770c364385c88c1515274f4ab3a2", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "aef6f60c344334f80cd48095f8bf8ba14ac0770c364385c88c1515274f4ab3a2", kill_on_drop: false }`
[INFO] [stdout] aef6f60c344334f80cd48095f8bf8ba14ac0770c364385c88c1515274f4ab3a2
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "test" "--frozen" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }`
[INFO] [stdout] e981d85fe8813c377c03b40ea74cd26e76902d6aedf7da57160f6e3ce503cdb5
[INFO] running `Command { std: "docker" "start" "-a" "e981d85fe8813c377c03b40ea74cd26e76902d6aedf7da57160f6e3ce503cdb5", kill_on_drop: false }`
[INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]  --> src/range_compat.rs:3:7
[INFO] [stderr]   |
[INFO] [stderr] 3 | #[cfg(inclusive_range)]
[INFO] [stderr]   |       ^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stderr]   = help: consider using a Cargo feature instead
[INFO] [stderr]   = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]            [lints.rust]
[INFO] [stderr]            unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]   = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]  --> src/range_compat.rs:6:7
[INFO] [stderr]   |
[INFO] [stderr] 6 | #[cfg(inclusive_range)]
[INFO] [stderr]   |       ^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = help: consider using a Cargo feature instead
[INFO] [stderr]   = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]            [lints.rust]
[INFO] [stderr]            unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]   = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `int_128`
[INFO] [stderr]    --> src/storage.rs:330:7
[INFO] [stderr]     |
[INFO] [stderr] 330 | #[cfg(int_128)]
[INFO] [stderr]     |       ^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(int_128)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(int_128)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]   --> src/traits/bit_sliceable.rs:90:7
[INFO] [stderr]    |
[INFO] [stderr] 90 | #[cfg(inclusive_range)]
[INFO] [stderr]    |       ^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = help: consider using a Cargo feature instead
[INFO] [stderr]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]             [lints.rust]
[INFO] [stderr]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/traits/bit_sliceable.rs:104:7
[INFO] [stderr]     |
[INFO] [stderr] 104 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/traits/bit_sliceable.rs:147:7
[INFO] [stderr]     |
[INFO] [stderr] 147 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/traits/bit_sliceable.rs:156:7
[INFO] [stderr]     |
[INFO] [stderr] 156 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/slice.rs:487:7
[INFO] [stderr]     |
[INFO] [stderr] 487 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/slice.rs:504:7
[INFO] [stderr]     |
[INFO] [stderr] 504 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/slice.rs:555:7
[INFO] [stderr]     |
[INFO] [stderr] 555 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/slice.rs:564:7
[INFO] [stderr]     |
[INFO] [stderr] 564 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unnecessary parentheses around block return value
[INFO] [stderr]    --> src/slice.rs:112:17
[INFO] [stderr]     |
[INFO] [stderr] 112 |                 (chunk1 | (chunk2 << shift2))
[INFO] [stderr]     |                 ^                           ^
[INFO] [stderr]     |
[INFO] [stderr]     = note: `#[warn(unused_parens)]` on by default
[INFO] [stderr] help: remove these parentheses
[INFO] [stderr]     |
[INFO] [stderr] 112 -                 (chunk1 | (chunk2 << shift2))
[INFO] [stderr] 112 +                 chunk1 | (chunk2 << shift2)
[INFO] [stderr]     |
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/bit_vec/impls.rs:121:7
[INFO] [stderr]     |
[INFO] [stderr] 121 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/bit_vec/impls.rs:130:7
[INFO] [stderr]     |
[INFO] [stderr] 130 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/bit_vec/impls.rs:171:7
[INFO] [stderr]     |
[INFO] [stderr] 171 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/bit_vec/impls.rs:180:7
[INFO] [stderr]     |
[INFO] [stderr] 180 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `int_128`
[INFO] [stderr]   --> src/prims.rs:70:7
[INFO] [stderr]    |
[INFO] [stderr] 70 | #[cfg(int_128)]
[INFO] [stderr]    |       ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = help: consider using a Cargo feature instead
[INFO] [stderr]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]             [lints.rust]
[INFO] [stderr]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(int_128)'] }
[INFO] [stderr]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(int_128)");` to the top of the `build.rs`
[INFO] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:252:7
[INFO] [stderr]     |
[INFO] [stderr] 252 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:263:7
[INFO] [stderr]     |
[INFO] [stderr] 263 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:309:7
[INFO] [stderr]     |
[INFO] [stderr] 309 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:320:7
[INFO] [stderr]     |
[INFO] [stderr] 320 | #[cfg(inclusive_range)]
[INFO] [stderr]     |       ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unnecessary parentheses around block return value
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:205:9
[INFO] [stderr]     |
[INFO] [stderr] 205 |         (start + len - real_start)
[INFO] [stderr]     |         ^                        ^
[INFO] [stderr]     |
[INFO] [stderr] help: remove these parentheses
[INFO] [stderr]     |
[INFO] [stderr] 205 -         (start + len - real_start)
[INFO] [stderr] 205 +         start + len - real_start
[INFO] [stderr]     |
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stderr]     |
[INFO] [stderr] 121 |               #[cfg(inclusive_range)]
[INFO] [stderr]     |                     ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:145:1
[INFO] [stderr]     |
[INFO] [stderr] 145 | / impl_bit_sliceable_adapter! {
[INFO] [stderr] 146 | |     impl['a, T: Bits] BitSliceable for &'a BitNot<T>;
[INFO] [stderr] 147 | | }
[INFO] [stderr]     | |_- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stderr]     |
[INFO] [stderr] 132 |               #[cfg(inclusive_range)]
[INFO] [stderr]     |                     ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:145:1
[INFO] [stderr]     |
[INFO] [stderr] 145 | / impl_bit_sliceable_adapter! {
[INFO] [stderr] 146 | |     impl['a, T: Bits] BitSliceable for &'a BitNot<T>;
[INFO] [stderr] 147 | | }
[INFO] [stderr]     | |_- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stderr]     |
[INFO] [stderr] 121 |             #[cfg(inclusive_range)]
[INFO] [stderr]     |                   ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:221:1
[INFO] [stderr]     |
[INFO] [stderr] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stderr]     | --------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stderr]     |
[INFO] [stderr] 132 |             #[cfg(inclusive_range)]
[INFO] [stderr]     |                   ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:221:1
[INFO] [stderr]     |
[INFO] [stderr] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stderr]     | --------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stderr]     |
[INFO] [stderr] 121 |             #[cfg(inclusive_range)]
[INFO] [stderr]     |                   ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:222:1
[INFO] [stderr]     |
[INFO] [stderr] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stderr]     | --------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stderr]     |
[INFO] [stderr] 132 |             #[cfg(inclusive_range)]
[INFO] [stderr]     |                   ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:222:1
[INFO] [stderr]     |
[INFO] [stderr] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stderr]     | --------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stderr]     |
[INFO] [stderr] 121 |             #[cfg(inclusive_range)]
[INFO] [stderr]     |                   ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:223:1
[INFO] [stderr]     |
[INFO] [stderr] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stderr]     |
[INFO] [stderr] 132 |             #[cfg(inclusive_range)]
[INFO] [stderr]     |                   ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:223:1
[INFO] [stderr]     |
[INFO] [stderr] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stderr]     |
[INFO] [stderr] 121 |               #[cfg(inclusive_range)]
[INFO] [stderr]     |                     ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:269:1
[INFO] [stderr]     |
[INFO] [stderr] 269 | / impl_bit_sliceable_adapter! {
[INFO] [stderr] 270 | |     impl['a, T: Bits, U: Bits<Block = T::Block>,
[INFO] [stderr] 271 | |          F: Fn(T::Block, T::Block) -> T::Block]
[INFO] [stderr] 272 | |         BitSliceable for &'a BitZip<T, U, F>;
[INFO] [stderr] 273 | | }
[INFO] [stderr]     | |_- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stderr]     |
[INFO] [stderr] 132 |               #[cfg(inclusive_range)]
[INFO] [stderr]     |                     ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:269:1
[INFO] [stderr]     |
[INFO] [stderr] 269 | / impl_bit_sliceable_adapter! {
[INFO] [stderr] 270 | |     impl['a, T: Bits, U: Bits<Block = T::Block>,
[INFO] [stderr] 271 | |          F: Fn(T::Block, T::Block) -> T::Block]
[INFO] [stderr] 272 | |         BitSliceable for &'a BitZip<T, U, F>;
[INFO] [stderr] 273 | | }
[INFO] [stderr]     | |_- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stderr]     |
[INFO] [stderr] 121 |               #[cfg(inclusive_range)]
[INFO] [stderr]     |                     ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/bit_fill.rs:74:1
[INFO] [stderr]     |
[INFO] [stderr] 74  | / impl_bit_sliceable_adapter! {
[INFO] [stderr] 75  | |     impl[Block: BlockType] BitSliceable for BitFill<Block>;
[INFO] [stderr] 76  | |     impl['a, Block: BlockType] BitSliceable for &'a BitFill<Block>;
[INFO] [stderr] 77  | | }
[INFO] [stderr]     | |_- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stderr]     |
[INFO] [stderr] 132 |               #[cfg(inclusive_range)]
[INFO] [stderr]     |                     ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/bit_fill.rs:74:1
[INFO] [stderr]     |
[INFO] [stderr] 74  | / impl_bit_sliceable_adapter! {
[INFO] [stderr] 75  | |     impl[Block: BlockType] BitSliceable for BitFill<Block>;
[INFO] [stderr] 76  | |     impl['a, Block: BlockType] BitSliceable for &'a BitFill<Block>;
[INFO] [stderr] 77  | | }
[INFO] [stderr]     | |_- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:121:19
[INFO] [stderr]     |
[INFO] [stderr] 121 |               #[cfg(inclusive_range)]
[INFO] [stderr]     |                     ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/bit_concat.rs:73:1
[INFO] [stderr]     |
[INFO] [stderr] 73  | / impl_bit_sliceable_adapter! {
[INFO] [stderr] 74  | |     impl[T: Bits, U: Bits<Block = T::Block>] BitSliceable for BitConcat<T, U>;
[INFO] [stderr] 75  | |     impl['a, T: Bits, U: Bits<Block = T::Block>] BitSliceable for &'a BitConcat<T, U>;
[INFO] [stderr] 76  | | }
[INFO] [stderr]     | |_- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:132:19
[INFO] [stderr]     |
[INFO] [stderr] 132 |               #[cfg(inclusive_range)]
[INFO] [stderr]     |                     ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/bit_concat.rs:73:1
[INFO] [stderr]     |
[INFO] [stderr] 73  | / impl_bit_sliceable_adapter! {
[INFO] [stderr] 74  | |     impl[T: Bits, U: Bits<Block = T::Block>] BitSliceable for BitConcat<T, U>;
[INFO] [stderr] 75  | |     impl['a, T: Bits, U: Bits<Block = T::Block>] BitSliceable for &'a BitConcat<T, U>;
[INFO] [stderr] 76  | | }
[INFO] [stderr]     | |_- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]   --> src/traits/bits.rs:62:17
[INFO] [stderr]    |
[INFO] [stderr] 62 | /                 format!("Bits::get_block: out of bounds ({}/{})",
[INFO] [stderr] 63 | |                         position, self.block_len()));
[INFO] [stderr]    | |___________________________________________________^
[INFO] [stderr]    |
[INFO] [stderr]    = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]    = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]    = note: `#[warn(non_fmt_panics)]` on by default
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]    |
[INFO] [stderr] 62 ~                 "Bits::get_block: out of bounds ({}/{})",
[INFO] [stderr] 63 ~                         position, self.block_len());
[INFO] [stderr]    |
[INFO] [stderr] 
[INFO] [stderr] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stderr]    --> src/bit_vec/mod.rs:497:21
[INFO] [stderr]     |
[INFO] [stderr] 497 |     pub fn as_slice(&self) -> BitSlice<Block> {
[INFO] [stderr]     |                     ^^^^^     --------------- the lifetime gets resolved as `'_`
[INFO] [stderr]     |                     |
[INFO] [stderr]     |                     this lifetime flows to the output
[INFO] [stderr]     |
[INFO] [stderr]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stderr] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stderr]     |
[INFO] [stderr] 497 |     pub fn as_slice(&self) -> BitSlice<'_, Block> {
[INFO] [stderr]     |                                        +++
[INFO] [stderr] 
[INFO] [stderr] warning: lifetime flowing from input to output with different syntax can be confusing
[INFO] [stderr]    --> src/bit_vec/mod.rs:523:25
[INFO] [stderr]     |
[INFO] [stderr] 523 |     pub fn as_mut_slice(&mut self) -> BitSliceMut<Block> {
[INFO] [stderr]     |                         ^^^^^^^^^     ------------------ the lifetime gets resolved as `'_`
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         this lifetime flows to the output
[INFO] [stderr]     |
[INFO] [stderr] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths
[INFO] [stderr]     |
[INFO] [stderr] 523 |     pub fn as_mut_slice(&mut self) -> BitSliceMut<'_, Block> {
[INFO] [stderr]     |                                                   +++
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stderr]     |
[INFO] [stderr] 90  |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:145:1
[INFO] [stderr]     |
[INFO] [stderr] 145 | / impl_bit_sliceable_adapter! {
[INFO] [stderr] 146 | |     impl['a, T: Bits] BitSliceable for &'a BitNot<T>;
[INFO] [stderr] 147 | | }
[INFO] [stderr]     | |_- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]     |
[INFO] [stderr] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stderr] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stderr]     |
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> src/adapter/logic.rs:172:26
[INFO] [stderr]     |
[INFO] [stderr] 172 |                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stderr]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stderr]     | --------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]     |
[INFO] [stderr] 172 -                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stderr] 172 +                          "{}::get_bit: out of bounds", stringify!($target) );
[INFO] [stderr]     |
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> src/adapter/logic.rs:178:26
[INFO] [stderr]     |
[INFO] [stderr] 178 |                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stderr]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stderr]     | --------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]     |
[INFO] [stderr] 178 -                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stderr] 178 +                          "{}::get_block: out of bounds", stringify!($target) );
[INFO] [stderr]     |
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stderr]     |
[INFO] [stderr] 90  | ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stderr]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:221:1
[INFO] [stderr]     |
[INFO] [stderr] 221 | impl_bits_bin_op!(BitAnd as & &&);
[INFO] [stderr]     | --------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]     |
[INFO] [stderr] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stderr] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stderr]     |
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> src/adapter/logic.rs:172:26
[INFO] [stderr]     |
[INFO] [stderr] 172 |                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stderr]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stderr]     | --------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]     |
[INFO] [stderr] 172 -                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stderr] 172 +                          "{}::get_bit: out of bounds", stringify!($target) );
[INFO] [stderr]     |
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> src/adapter/logic.rs:178:26
[INFO] [stderr]     |
[INFO] [stderr] 178 |                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stderr]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stderr]     | --------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]     |
[INFO] [stderr] 178 -                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stderr] 178 +                          "{}::get_block: out of bounds", stringify!($target) );
[INFO] [stderr]     |
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stderr]     |
[INFO] [stderr] 90  | ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stderr]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:222:1
[INFO] [stderr]     |
[INFO] [stderr] 222 | impl_bits_bin_op!(BitOr  as | ||);
[INFO] [stderr]     | --------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]     |
[INFO] [stderr] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stderr] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stderr]     |
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> src/adapter/logic.rs:172:26
[INFO] [stderr]     |
[INFO] [stderr] 172 |                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stderr]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]     |
[INFO] [stderr] 172 -                          format!("{}::get_bit: out of bounds", stringify!($target)) );
[INFO] [stderr] 172 +                          "{}::get_bit: out of bounds", stringify!($target) );
[INFO] [stderr]     |
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> src/adapter/logic.rs:178:26
[INFO] [stderr]     |
[INFO] [stderr] 178 |                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stderr]     |                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]     = note: this warning originates in the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]     |
[INFO] [stderr] 178 -                          format!("{}::get_block: out of bounds", stringify!($target)) );
[INFO] [stderr] 178 +                          "{}::get_block: out of bounds", stringify!($target) );
[INFO] [stderr]     |
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stderr]     |
[INFO] [stderr] 90  | ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stderr]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:223:1
[INFO] [stderr]     |
[INFO] [stderr] 223 | impl_bits_bin_op!(BitXor as ^ ^);
[INFO] [stderr]     | -------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` which comes from the expansion of the macro `impl_bits_bin_op` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]     |
[INFO] [stderr] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stderr] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stderr]     |
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]    --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stderr]     |
[INFO] [stderr] 90  |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]    ::: src/adapter/logic.rs:269:1
[INFO] [stderr]     |
[INFO] [stderr] 269 | / impl_bit_sliceable_adapter! {
[INFO] [stderr] 270 | |     impl['a, T: Bits, U: Bits<Block = T::Block>,
[INFO] [stderr] 271 | |          F: Fn(T::Block, T::Block) -> T::Block]
[INFO] [stderr] 272 | |         BitSliceable for &'a BitZip<T, U, F>;
[INFO] [stderr] 273 | | }
[INFO] [stderr]     | |_- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]     = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]     = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]     = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]     |
[INFO] [stderr] 90  -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stderr] 90  +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stderr]     |
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]   --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stderr]    |
[INFO] [stderr] 90 |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stderr]    |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]   ::: src/adapter/bit_fill.rs:74:1
[INFO] [stderr]    |
[INFO] [stderr] 74 | / impl_bit_sliceable_adapter! {
[INFO] [stderr] 75 | |     impl[Block: BlockType] BitSliceable for BitFill<Block>;
[INFO] [stderr] 76 | |     impl['a, Block: BlockType] BitSliceable for &'a BitFill<Block>;
[INFO] [stderr] 77 | | }
[INFO] [stderr]    | |_- in this macro invocation
[INFO] [stderr]    |
[INFO] [stderr]    = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]    = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]    = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]    |
[INFO] [stderr] 90 -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stderr] 90 +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stderr]    |
[INFO] [stderr] 
[INFO] [stderr] warning: panic message is not a string literal
[INFO] [stderr]   --> src/adapter/bit_slice_adapter.rs:90:30
[INFO] [stderr]    |
[INFO] [stderr] 90 |   ...                   format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stderr]    |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]   ::: src/adapter/bit_concat.rs:73:1
[INFO] [stderr]    |
[INFO] [stderr] 73 | / impl_bit_sliceable_adapter! {
[INFO] [stderr] 74 | |     impl[T: Bits, U: Bits<Block = T::Block>] BitSliceable for BitConcat<T, U>;
[INFO] [stderr] 75 | |     impl['a, T: Bits, U: Bits<Block = T::Block>] BitSliceable for &'a BitConcat<T, U>;
[INFO] [stderr] 76 | | }
[INFO] [stderr]    | |_- in this macro invocation
[INFO] [stderr]    |
[INFO] [stderr]    = note: this usage of `assert!()` is deprecated; it will be a hard error in Rust 2021
[INFO] [stderr]    = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/panic-macro-consistency.html>
[INFO] [stderr]    = note: the `assert!()` macro supports formatting, so there's no need for the `format!()` macro here
[INFO] [stderr]    = note: this warning originates in the macro `impl_bit_sliceable_adapter` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] help: remove the `format!(..)` macro call
[INFO] [stderr]    |
[INFO] [stderr] 90 -                              format!("{}::slice: bad range", stringify!($target)) );
[INFO] [stderr] 90 +                              "{}::slice: bad range", stringify!($target) );
[INFO] [stderr]    |
[INFO] [stderr] 
[INFO] [stderr] warning: `bv` (lib) generated 52 warnings (run `cargo fix --lib -p bv` to apply 18 suggestions)
[INFO] [stderr] warning: unexpected `cfg` condition name: `inclusive_range`
[INFO] [stderr]    --> src/slice.rs:753:11
[INFO] [stderr]     |
[INFO] [stderr] 753 |     #[cfg(inclusive_range)]
[INFO] [stderr]     |           ^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(inclusive_range)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(inclusive_range)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition name: `int_128`
[INFO] [stderr]    --> src/prims.rs:134:11
[INFO] [stderr]     |
[INFO] [stderr] 134 |     #[cfg(int_128)]
[INFO] [stderr]     |           ^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = help: consider using a Cargo feature instead
[INFO] [stderr]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stderr]              [lints.rust]
[INFO] [stderr]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(int_128)'] }
[INFO] [stderr]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(int_128)");` to the top of the `build.rs`
[INFO] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] 
[INFO] [stderr] warning: `bv` (lib test) generated 54 warnings (52 duplicates)
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.09s
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/bv-d1644e149da92b68)
[INFO] [stdout] 
[INFO] [stdout] running 70 tests
[INFO] [stdout] test adapter::test::mixed_equality ... ok
[INFO] [stdout] test adapter::test::and_with_same_offset ... ok
[INFO] [stdout] test adapter::test::simple_and ... ok
[INFO] [stdout] test adapter::test::append ... ok
[INFO] [stdout] test adapter::test::simple_not ... ok
[INFO] [stdout] test adapter::test::slice_adapter_mutation ... ok
[INFO] [stdout] test bit_vec::test::disequality ... ok
[INFO] [stdout] test bit_vec::test::bit_slicing ... ok
[INFO] [stdout] test bit_vec::test::clear_and_is_empty ... ok
[INFO] [stdout] test adapter::test::slice_adapter ... ok
[INFO] [stdout] test bit_vec::test::as_mut_slice ... ok
[INFO] [stdout] test adapter::test::pad ... ok
[INFO] [stdout] test adapter::test::and_with_different_offset ... ok
[INFO] [stdout] test bit_vec::test::from_bits ... ok
[INFO] [stdout] test bit_vec::test::from_bits_slice ... ok
[INFO] [stdout] test bit_vec::test::into_boxed_slice ... ok
[INFO] [stdout] test bit_vec::test::mixed_equality ... ok
[INFO] [stdout] test bit_vec::test::pop ... ok
[INFO] [stdout] test bit_vec::test::push_bit_and_pop_bit ... ok
[INFO] [stdout] test bit_vec::test::resize ... ok
[INFO] [stdout] test bit_vec::test::set_bits_one_block_fastpath ... ok
[INFO] [stdout] test bit_vec::test::set_through_slice ... ok
[INFO] [stdout] test bit_vec::test::shrink_to_fit ... ok
[INFO] [stdout] test bit_vec::test::truncate ... ok
[INFO] [stdout] test iter::test::different ... ok
[INFO] [stdout] test iter::test::empty ... ok
[INFO] [stdout] test iter::test::same ... ok
[INFO] [stdout] test macros::bit_vec_macro_allows_trailing_comma ... ok
[INFO] [stdout] test macros::type_1_hygiene ... ok
[INFO] [stdout] test prims::test::bit_len ... ok
[INFO] [stdout] test prims::test::block_len ... ok
[INFO] [stdout] test prims::test::get_bit ... ok
[INFO] [stdout] test prims::test::set_bit ... ok
[INFO] [stdout] test iter::test::different_lengths ... ok
[INFO] [stdout] test prims::test::prop_get_block_u32 ... ok
[INFO] [stdout] test prims::test::prop_get_block_u8 ... ok
[INFO] [stdout] test slice::test::bit_slice_index ... ok
[INFO] [stdout] test slice::test::debug_for_bit_slice ... ok
[INFO] [stdout] test storage::test::block_bits ... ok
[INFO] [stdout] test storage::test::get_bit ... ok
[INFO] [stdout] test prims::test::get_bits ... ok
[INFO] [stdout] test prims::test::u128_feature ... ok
[INFO] [stdout] test slice::test::bit_slice_update_across_blocks ... ok
[INFO] [stdout] test slice::test::range_to_inclusive ... ok
[INFO] [stdout] test storage::test::ceil_lg ... ok
[INFO] [stdout] test storage::test::floor_lg ... ok
[INFO] [stdout] test slice::test::bit_slice_from_slice ... ok
[INFO] [stdout] test storage::test::get_bits ... ok
[INFO] [stdout] test storage::test::lg_nbits ... ok
[INFO] [stdout] test storage::test::low_mask ... ok
[INFO] [stdout] test storage::test::nbits ... ok
[INFO] [stdout] test storage::test::nth_mask ... ok
[INFO] [stdout] test storage::test::prop_ceil_div_nbits1 ... ok
[INFO] [stdout] test storage::test::prop_ceil_div_nbits2 ... ok
[INFO] [stdout] test storage::test::prop_div_nbits ... ok
[INFO] [stdout] test storage::test::with_bit ... ok
[INFO] [stdout] test storage::test::prop_mod_nbits ... ok
[INFO] [stdout] test storage::test::prop_mul_nbits ... ok
[INFO] [stdout] test storage::test::with_bits ... ok
[INFO] [stdout] test traits::test::bogus_get_bits_vec_bool_works_okay ... ok
[INFO] [stdout] test traits::bits_mut_ext::test::bit_xor_assign_slice ... ok
[INFO] [stdout] test traits::bits_mut_ext::test::bit_and_assign ... ok
[INFO] [stdout] test traits::test::bit_slicing ... ok
[INFO] [stdout] test traits::test::set_block ... ok
[INFO] [stdout] test traits::test::set_block_slice ... ok
[INFO] [stdout] test traits::test::vec_u8_is_bit_vec ... ok
[INFO] [stdout] test traits::test::vec_u8_is_bit_vec_mut ... ok
[INFO] [stdout] test traits::test::bogus_get_bits_vec_bool_oob - should panic ... ok
[INFO] [stdout] test traits::bits_mut_ext::test::bit_and_assign_bad_sizes - should panic ... ok
[INFO] [stdout] test traits::test::get_block_oob - should panic ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 70 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.14s
[INFO] [stdout] 
[INFO] [stderr]      Running tests/random_adapter.rs (/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/random_adapter-e67910d9e50925a8)
[INFO] [stdout] 
[INFO] [stdout] running 5 tests
[INFO] [stdout] test prop_u8 ... ok
[INFO] [stdout] test prop_u16 ... ok
[INFO] [stdout] test prop_usize ... ok
[INFO] [stdout] test prop_u32 ... ok
[INFO] [stdout] test prop_u64 ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 5 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.06s
[INFO] [stdout] 
[INFO] running `Command { std: "docker" "inspect" "e981d85fe8813c377c03b40ea74cd26e76902d6aedf7da57160f6e3ce503cdb5", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "e981d85fe8813c377c03b40ea74cd26e76902d6aedf7da57160f6e3ce503cdb5", kill_on_drop: false }`
[INFO] [stdout] e981d85fe8813c377c03b40ea74cd26e76902d6aedf7da57160f6e3ce503cdb5