[INFO] fetching crate bv 0.11.1...
[INFO] checking bv-0.11.1 against master#ab869e094a907cc5d19b4080f22eccaf347f1f95 for pr-129604
[INFO] extracting crate bv 0.11.1 into /workspace/builds/worker-7-tc1/source
[INFO] validating manifest of crates.io crate bv 0.11.1 on toolchain ab869e094a907cc5d19b4080f22eccaf347f1f95
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+ab869e094a907cc5d19b4080f22eccaf347f1f95" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[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-7-tc1/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+ab869e094a907cc5d19b4080f22eccaf347f1f95" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 41 packages to latest compatible versions
[INFO] [stderr]       Adding env_logger v0.5.13 (latest: v0.11.5)
[INFO] [stderr]       Adding hermit-abi v0.1.19 (latest: v0.4.0)
[INFO] [stderr]       Adding humantime v1.3.0 (latest: v2.1.0)
[INFO] [stderr]       Adding quick-error v1.2.3 (latest: v2.0.1)
[INFO] [stderr]       Adding quickcheck v0.6.2 (latest: v1.0.3)
[INFO] [stderr]       Adding rand v0.4.6 (latest: v0.8.5)
[INFO] [stderr]       Adding rand_core v0.3.1 (latest: v0.6.4)
[INFO] [stderr]       Adding rand_core v0.4.2 (latest: v0.6.4)
[INFO] [stderr]       Adding rdrand v0.4.0 (latest: v0.8.3)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+ab869e094a907cc5d19b4080f22eccaf347f1f95" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2021
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded rand_core v0.4.2
[INFO] [stderr]   Downloaded env_logger v0.5.13
[INFO] [stderr]   Downloaded quickcheck v0.6.2
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-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:923055f121b5182466d55868a8b05e67af8ba4a3a3f6bad814e953ca3cd3ac2a" "/opt/rustwide/cargo-home/bin/cargo" "+ab869e094a907cc5d19b4080f22eccaf347f1f95" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] d9030da37f247419ae7acfdc0894fead2a6001ee56e5474f073370a3ae76d078
[INFO] running `Command { std: "docker" "start" "-a" "d9030da37f247419ae7acfdc0894fead2a6001ee56e5474f073370a3ae76d078", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "d9030da37f247419ae7acfdc0894fead2a6001ee56e5474f073370a3ae76d078", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "d9030da37f247419ae7acfdc0894fead2a6001ee56e5474f073370a3ae76d078", kill_on_drop: false }`
[INFO] [stdout] d9030da37f247419ae7acfdc0894fead2a6001ee56e5474f073370a3ae76d078
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-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:923055f121b5182466d55868a8b05e67af8ba4a3a3f6bad814e953ca3cd3ac2a" "/opt/rustwide/cargo-home/bin/cargo" "+ab869e094a907cc5d19b4080f22eccaf347f1f95" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 86c1bf555b15b9410b83d75f92478c81b420c3abf30652b8a6e88fbb1a6c1fed
[INFO] running `Command { std: "docker" "start" "-a" "86c1bf555b15b9410b83d75f92478c81b420c3abf30652b8a6e88fbb1a6c1fed", kill_on_drop: false }`
[INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2021
[INFO] [stderr]    Compiling libc v0.2.158
[INFO] [stderr]     Checking memchr v2.7.4
[INFO] [stderr]     Checking regex-syntax v0.8.4
[INFO] [stderr]     Checking quick-error v1.2.3
[INFO] [stderr]    Compiling feature-probe v0.1.1
[INFO] [stderr]     Checking log v0.4.22
[INFO] [stderr]     Checking termcolor v1.4.1
[INFO] [stderr]     Checking humantime v1.3.0
[INFO] [stderr]    Compiling bv v0.11.1 (/opt/rustwide/workdir)
[INFO] [stderr]     Checking aho-corasick v1.1.3
[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: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows`
[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] [stderr]     Checking atty v0.2.14
[INFO] [stderr]     Checking rand v0.4.6
[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: 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] [stdout] warning: 50 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Checking regex-automata v0.4.7
[INFO] [stderr]     Checking regex v1.10.6
[INFO] [stderr]     Checking env_logger v0.5.13
[INFO] [stderr]     Checking quickcheck v0.6.2
[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: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows`
[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: 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] [stdout] warning: 52 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 8.02s
[INFO] running `Command { std: "docker" "inspect" "86c1bf555b15b9410b83d75f92478c81b420c3abf30652b8a6e88fbb1a6c1fed", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "86c1bf555b15b9410b83d75f92478c81b420c3abf30652b8a6e88fbb1a6c1fed", kill_on_drop: false }`
[INFO] [stdout] 86c1bf555b15b9410b83d75f92478c81b420c3abf30652b8a6e88fbb1a6c1fed