[INFO] fetching crate num-traits 0.2.17...
[INFO] checking num-traits-0.2.17 against nightly-2024-02-05 for check-cfg
[INFO] extracting crate num-traits 0.2.17 into /workspace/builds/worker-6-tc1/source
[INFO] validating manifest of crates.io crate num-traits 0.2.17 on toolchain nightly-2024-02-05
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate num-traits 0.2.17
[INFO] finished tweaking crates.io crate num-traits 0.2.17
[INFO] tweaked toml for crates.io crate num-traits 0.2.17 written to /workspace/builds/worker-6-tc1/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-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:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-02-05" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] e8a59949ac11f739d02864cfe9ce7dd335a6aec3719bf5c811ad559829749f94
[INFO] running `Command { std: "docker" "start" "-a" "e8a59949ac11f739d02864cfe9ce7dd335a6aec3719bf5c811ad559829749f94", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "e8a59949ac11f739d02864cfe9ce7dd335a6aec3719bf5c811ad559829749f94", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "e8a59949ac11f739d02864cfe9ce7dd335a6aec3719bf5c811ad559829749f94", kill_on_drop: false }`
[INFO] [stdout] e8a59949ac11f739d02864cfe9ce7dd335a6aec3719bf5c811ad559829749f94
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-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:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-02-05" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 83632549e08c759bba52de27b4b5ffe882223c604486abcfa48b7846290c927d
[INFO] running `Command { std: "docker" "start" "-a" "83632549e08c759bba52de27b4b5ffe882223c604486abcfa48b7846290c927d", kill_on_drop: false }`
[INFO] [stderr]    Compiling num-traits v0.2.17 (/opt/rustwide/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.23s
[INFO] running `Command { std: "docker" "inspect" "83632549e08c759bba52de27b4b5ffe882223c604486abcfa48b7846290c927d", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "83632549e08c759bba52de27b4b5ffe882223c604486abcfa48b7846290c927d", kill_on_drop: false }`
[INFO] [stdout] 83632549e08c759bba52de27b4b5ffe882223c604486abcfa48b7846290c927d
[INFO] checking num-traits-0.2.17 against nightly-2024-02-05+rustflags=-Dunexpected_cfgs+cargoflags=-Zcheck-cfg for check-cfg
[INFO] extracting crate num-traits 0.2.17 into /workspace/builds/worker-6-tc2/source
[INFO] validating manifest of crates.io crate num-traits 0.2.17 on toolchain nightly-2024-02-05
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate num-traits 0.2.17
[INFO] finished tweaking crates.io crate num-traits 0.2.17
[INFO] tweaked toml for crates.io crate num-traits 0.2.17 written to /workspace/builds/worker-6-tc2/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2024-02-05" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/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:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-02-05" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] f44851c33deb191c15a24bfea69f226adcbcce090eaf7540932a2d6b876c2848
[INFO] running `Command { std: "docker" "start" "-a" "f44851c33deb191c15a24bfea69f226adcbcce090eaf7540932a2d6b876c2848", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "f44851c33deb191c15a24bfea69f226adcbcce090eaf7540932a2d6b876c2848", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "f44851c33deb191c15a24bfea69f226adcbcce090eaf7540932a2d6b876c2848", kill_on_drop: false }`
[INFO] [stdout] f44851c33deb191c15a24bfea69f226adcbcce090eaf7540932a2d6b876c2848
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/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 -Dunexpected_cfgs" "-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:2788e3201cd34a07e3172128adcd8b3090168a8e3bcc40d7c032b9dda1df7d1c" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2024-02-05" "check" "--frozen" "--all" "--all-targets" "--message-format=json" "-Zcheck-cfg", kill_on_drop: false }`
[INFO] [stdout] 2c8770a3686124536bf74aef6c6b9308357691a87c1cf99f97eb6066d898f165
[INFO] running `Command { std: "docker" "start" "-a" "2c8770a3686124536bf74aef6c6b9308357691a87c1cf99f97eb6066d898f165", kill_on_drop: false }`
[INFO] [stderr]    Compiling num-traits v0.2.17 (/opt/rustwide/workdir)
[INFO] [stdout] error: unexpected `cfg` condition name: `has_to_int_unchecked`
[INFO] [stdout]    --> src/cast.rs:280:7
[INFO] [stdout]     |
[INFO] [stdout] 280 | #[cfg(has_to_int_unchecked)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: expected names are: `debug_assertions`, `doc`, `doctest`, `feature`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `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`, `unix`, `windows`
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_to_int_unchecked)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: requested on the command line with `-D unexpected-cfgs`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_to_int_unchecked`
[INFO] [stdout]    --> src/cast.rs:289:11
[INFO] [stdout]     |
[INFO] [stdout] 289 | #[cfg(not(has_to_int_unchecked))]
[INFO] [stdout]     |           ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_to_int_unchecked)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_is_subnormal`
[INFO] [stdout]    --> src/float.rs:802:11
[INFO] [stdout]     |
[INFO] [stdout] 802 |     #[cfg(has_is_subnormal)]
[INFO] [stdout]     |           ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_is_subnormal)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_is_subnormal`
[INFO] [stdout]    --> src/float.rs:867:11
[INFO] [stdout]     |
[INFO] [stdout] 867 |     #[cfg(has_is_subnormal)]
[INFO] [stdout]     |           ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_is_subnormal)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_copysign`
[INFO] [stdout]     --> src/float.rs:1948:19
[INFO] [stdout]      |
[INFO] [stdout] 1948 |             #[cfg(has_copysign)]
[INFO] [stdout]      |                   ^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 2046 | float_impl_std!(f32 integer_decode_f32);
[INFO] [stdout]      | --------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_copysign)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `float_impl_std` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_is_subnormal`
[INFO] [stdout]     --> src/float.rs:1953:19
[INFO] [stdout]      |
[INFO] [stdout] 1953 |             #[cfg(has_is_subnormal)]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 2046 | float_impl_std!(f32 integer_decode_f32);
[INFO] [stdout]      | --------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_is_subnormal)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `float_impl_std` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_copysign`
[INFO] [stdout]     --> src/float.rs:1948:19
[INFO] [stdout]      |
[INFO] [stdout] 1948 |             #[cfg(has_copysign)]
[INFO] [stdout]      |                   ^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 2048 | float_impl_std!(f64 integer_decode_f64);
[INFO] [stdout]      | --------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_copysign)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `float_impl_std` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_is_subnormal`
[INFO] [stdout]     --> src/float.rs:1953:19
[INFO] [stdout]      |
[INFO] [stdout] 1953 |             #[cfg(has_is_subnormal)]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 2048 | float_impl_std!(f64 integer_decode_f64);
[INFO] [stdout]      | --------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_is_subnormal)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `float_impl_std` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 499 | prim_int_impl!(u8, i8, u8);
[INFO] [stdout]     | -------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 499 | prim_int_impl!(u8, i8, u8);
[INFO] [stdout]     | -------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 499 | prim_int_impl!(u8, i8, u8);
[INFO] [stdout]     | -------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 500 | prim_int_impl!(u16, i16, u16);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 500 | prim_int_impl!(u16, i16, u16);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 500 | prim_int_impl!(u16, i16, u16);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 501 | prim_int_impl!(u32, i32, u32);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 501 | prim_int_impl!(u32, i32, u32);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 501 | prim_int_impl!(u32, i32, u32);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 502 | prim_int_impl!(u64, i64, u64);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 502 | prim_int_impl!(u64, i64, u64);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 502 | prim_int_impl!(u64, i64, u64);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 503 | prim_int_impl!(u128, i128, u128);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 503 | prim_int_impl!(u128, i128, u128);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 503 | prim_int_impl!(u128, i128, u128);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 504 | prim_int_impl!(usize, isize, usize);
[INFO] [stdout]     | ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 504 | prim_int_impl!(usize, isize, usize);
[INFO] [stdout]     | ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 504 | prim_int_impl!(usize, isize, usize);
[INFO] [stdout]     | ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 505 | prim_int_impl!(i8, i8, u8);
[INFO] [stdout]     | -------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 505 | prim_int_impl!(i8, i8, u8);
[INFO] [stdout]     | -------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 505 | prim_int_impl!(i8, i8, u8);
[INFO] [stdout]     | -------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 506 | prim_int_impl!(i16, i16, u16);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 506 | prim_int_impl!(i16, i16, u16);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 506 | prim_int_impl!(i16, i16, u16);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 507 | prim_int_impl!(i32, i32, u32);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 507 | prim_int_impl!(i32, i32, u32);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 507 | prim_int_impl!(i32, i32, u32);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 508 | prim_int_impl!(i64, i64, u64);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 508 | prim_int_impl!(i64, i64, u64);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 508 | prim_int_impl!(i64, i64, u64);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 509 | prim_int_impl!(i128, i128, u128);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 509 | prim_int_impl!(i128, i128, u128);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 509 | prim_int_impl!(i128, i128, u128);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 510 | prim_int_impl!(isize, isize, usize);
[INFO] [stdout]     | ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 510 | prim_int_impl!(isize, isize, usize);
[INFO] [stdout]     | ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 510 | prim_int_impl!(isize, isize, usize);
[INFO] [stdout]     | ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]  --> src/ops/bytes.rs:5:11
[INFO] [stdout]   |
[INFO] [stdout] 5 | #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]   |           ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 321 | int_to_from_bytes_impl!(u8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 321 | int_to_from_bytes_impl!(u8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 321 | int_to_from_bytes_impl!(u8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 321 | int_to_from_bytes_impl!(u8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 322 | int_to_from_bytes_impl!(u16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 322 | int_to_from_bytes_impl!(u16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 322 | int_to_from_bytes_impl!(u16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 322 | int_to_from_bytes_impl!(u16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 323 | int_to_from_bytes_impl!(u32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 323 | int_to_from_bytes_impl!(u32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 323 | int_to_from_bytes_impl!(u32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 323 | int_to_from_bytes_impl!(u32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 324 | int_to_from_bytes_impl!(u64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 324 | int_to_from_bytes_impl!(u64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 324 | int_to_from_bytes_impl!(u64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 324 | int_to_from_bytes_impl!(u64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 325 | int_to_from_bytes_impl!(u128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 325 | int_to_from_bytes_impl!(u128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 325 | int_to_from_bytes_impl!(u128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 325 | int_to_from_bytes_impl!(u128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 327 | int_to_from_bytes_impl!(usize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 327 | int_to_from_bytes_impl!(usize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 327 | int_to_from_bytes_impl!(usize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 327 | int_to_from_bytes_impl!(usize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 331 | int_to_from_bytes_impl!(i8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 331 | int_to_from_bytes_impl!(i8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 331 | int_to_from_bytes_impl!(i8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 331 | int_to_from_bytes_impl!(i8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 332 | int_to_from_bytes_impl!(i16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 332 | int_to_from_bytes_impl!(i16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 332 | int_to_from_bytes_impl!(i16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 332 | int_to_from_bytes_impl!(i16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 333 | int_to_from_bytes_impl!(i32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 333 | int_to_from_bytes_impl!(i32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 333 | int_to_from_bytes_impl!(i32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 333 | int_to_from_bytes_impl!(i32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | int_to_from_bytes_impl!(i64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | int_to_from_bytes_impl!(i64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | int_to_from_bytes_impl!(i64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | int_to_from_bytes_impl!(i64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 335 | int_to_from_bytes_impl!(i128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 335 | int_to_from_bytes_impl!(i128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 335 | int_to_from_bytes_impl!(i128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 335 | int_to_from_bytes_impl!(i128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | int_to_from_bytes_impl!(isize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | int_to_from_bytes_impl!(isize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | int_to_from_bytes_impl!(isize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | int_to_from_bytes_impl!(isize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:155:15
[INFO] [stdout]     |
[INFO] [stdout] 155 |         #[cfg(has_float_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 341 | float_to_from_bytes_impl!(f32, 4);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:175:15
[INFO] [stdout]     |
[INFO] [stdout] 175 |         #[cfg(has_float_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 341 | float_to_from_bytes_impl!(f32, 4);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:195:19
[INFO] [stdout]     |
[INFO] [stdout] 195 |         #[cfg(not(has_float_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 341 | float_to_from_bytes_impl!(f32, 4);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:215:19
[INFO] [stdout]     |
[INFO] [stdout] 215 |         #[cfg(not(has_float_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 341 | float_to_from_bytes_impl!(f32, 4);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:155:15
[INFO] [stdout]     |
[INFO] [stdout] 155 |         #[cfg(has_float_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 342 | float_to_from_bytes_impl!(f64, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:175:15
[INFO] [stdout]     |
[INFO] [stdout] 175 |         #[cfg(has_float_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 342 | float_to_from_bytes_impl!(f64, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:195:19
[INFO] [stdout]     |
[INFO] [stdout] 195 |         #[cfg(not(has_float_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 342 | float_to_from_bytes_impl!(f64, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:215:19
[INFO] [stdout]     |
[INFO] [stdout] 215 |         #[cfg(not(has_float_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 342 | float_to_from_bytes_impl!(f64, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:122:11
[INFO] [stdout]     |
[INFO] [stdout] 122 | #[cfg(all(has_div_euclid, feature = "std"))]
[INFO] [stdout]     |           ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:125:15
[INFO] [stdout]     |
[INFO] [stdout] 125 | #[cfg(not(all(has_div_euclid, feature = "std")))]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:147:15
[INFO] [stdout]     |
[INFO] [stdout] 147 | #[cfg(not(all(has_div_euclid, feature = "std")))]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:72:19
[INFO] [stdout]     |
[INFO] [stdout] 72  |         #[cfg(not(has_div_euclid))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 119 | euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 119 | euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 119 | euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 119 | euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 119 | euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 119 | euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 119 | euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:104:19
[INFO] [stdout]     |
[INFO] [stdout] 104 |         #[cfg(not(has_div_euclid))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 120 | euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 120 | euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 120 | euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 120 | euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 120 | euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 120 | euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 120 | euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 123 | euclid_forward_impl!(f32 f64);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:200:19
[INFO] [stdout]     |
[INFO] [stdout] 200 |         #[cfg(not(has_div_euclid))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 250 | checked_euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 250 | checked_euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 250 | checked_euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 250 | checked_euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 250 | checked_euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 250 | checked_euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 250 | checked_euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:227:19
[INFO] [stdout]     |
[INFO] [stdout] 227 |         #[cfg(not(has_div_euclid))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 251 | checked_euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 251 | checked_euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 251 | checked_euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 251 | checked_euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 251 | checked_euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 251 | checked_euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 251 | checked_euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_to_int_unchecked`
[INFO] [stdout]    --> src/cast.rs:280:7
[INFO] [stdout]     |
[INFO] [stdout] 280 | #[cfg(has_to_int_unchecked)]
[INFO] [stdout]     |       ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: expected names are: `debug_assertions`, `doc`, `doctest`, `feature`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `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`, `unix`, `windows`
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_to_int_unchecked)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: requested on the command line with `-D unexpected-cfgs`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_to_int_unchecked`
[INFO] [stdout]    --> src/cast.rs:289:11
[INFO] [stdout]     |
[INFO] [stdout] 289 | #[cfg(not(has_to_int_unchecked))]
[INFO] [stdout]     |           ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_to_int_unchecked)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_is_subnormal`
[INFO] [stdout]    --> src/float.rs:802:11
[INFO] [stdout]     |
[INFO] [stdout] 802 |     #[cfg(has_is_subnormal)]
[INFO] [stdout]     |           ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_is_subnormal)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_is_subnormal`
[INFO] [stdout]    --> src/float.rs:867:11
[INFO] [stdout]     |
[INFO] [stdout] 867 |     #[cfg(has_is_subnormal)]
[INFO] [stdout]     |           ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_is_subnormal)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_copysign`
[INFO] [stdout]     --> src/float.rs:1948:19
[INFO] [stdout]      |
[INFO] [stdout] 1948 |             #[cfg(has_copysign)]
[INFO] [stdout]      |                   ^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 2046 | float_impl_std!(f32 integer_decode_f32);
[INFO] [stdout]      | --------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_copysign)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `float_impl_std` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_is_subnormal`
[INFO] [stdout]     --> src/float.rs:1953:19
[INFO] [stdout]      |
[INFO] [stdout] 1953 |             #[cfg(has_is_subnormal)]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 2046 | float_impl_std!(f32 integer_decode_f32);
[INFO] [stdout]      | --------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_is_subnormal)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `float_impl_std` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_copysign`
[INFO] [stdout]     --> src/float.rs:1948:19
[INFO] [stdout]      |
[INFO] [stdout] 1948 |             #[cfg(has_copysign)]
[INFO] [stdout]      |                   ^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 2048 | float_impl_std!(f64 integer_decode_f64);
[INFO] [stdout]      | --------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_copysign)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `float_impl_std` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_is_subnormal`
[INFO] [stdout]     --> src/float.rs:1953:19
[INFO] [stdout]      |
[INFO] [stdout] 1953 |             #[cfg(has_is_subnormal)]
[INFO] [stdout]      |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 2048 | float_impl_std!(f64 integer_decode_f64);
[INFO] [stdout]      | --------------------------------------- in this macro invocation
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_is_subnormal)");` to the top of a `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]      = note: this error originates in the macro `float_impl_std` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 499 | prim_int_impl!(u8, i8, u8);
[INFO] [stdout]     | -------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 499 | prim_int_impl!(u8, i8, u8);
[INFO] [stdout]     | -------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 499 | prim_int_impl!(u8, i8, u8);
[INFO] [stdout]     | -------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 500 | prim_int_impl!(u16, i16, u16);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 500 | prim_int_impl!(u16, i16, u16);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 500 | prim_int_impl!(u16, i16, u16);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 501 | prim_int_impl!(u32, i32, u32);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 501 | prim_int_impl!(u32, i32, u32);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 501 | prim_int_impl!(u32, i32, u32);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 502 | prim_int_impl!(u64, i64, u64);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 502 | prim_int_impl!(u64, i64, u64);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 502 | prim_int_impl!(u64, i64, u64);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 503 | prim_int_impl!(u128, i128, u128);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 503 | prim_int_impl!(u128, i128, u128);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 503 | prim_int_impl!(u128, i128, u128);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 504 | prim_int_impl!(usize, isize, usize);
[INFO] [stdout]     | ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 504 | prim_int_impl!(usize, isize, usize);
[INFO] [stdout]     | ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 504 | prim_int_impl!(usize, isize, usize);
[INFO] [stdout]     | ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 505 | prim_int_impl!(i8, i8, u8);
[INFO] [stdout]     | -------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 505 | prim_int_impl!(i8, i8, u8);
[INFO] [stdout]     | -------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 505 | prim_int_impl!(i8, i8, u8);
[INFO] [stdout]     | -------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 506 | prim_int_impl!(i16, i16, u16);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 506 | prim_int_impl!(i16, i16, u16);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 506 | prim_int_impl!(i16, i16, u16);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 507 | prim_int_impl!(i32, i32, u32);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 507 | prim_int_impl!(i32, i32, u32);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 507 | prim_int_impl!(i32, i32, u32);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 508 | prim_int_impl!(i64, i64, u64);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 508 | prim_int_impl!(i64, i64, u64);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 508 | prim_int_impl!(i64, i64, u64);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 509 | prim_int_impl!(i128, i128, u128);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 509 | prim_int_impl!(i128, i128, u128);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 509 | prim_int_impl!(i128, i128, u128);
[INFO] [stdout]     | -------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:407:19
[INFO] [stdout]     |
[INFO] [stdout] 407 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 510 | prim_int_impl!(isize, isize, usize);
[INFO] [stdout]     | ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_leading_trailing_ones`
[INFO] [stdout]    --> src/int.rs:418:19
[INFO] [stdout]     |
[INFO] [stdout] 418 |             #[cfg(has_leading_trailing_ones)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 510 | prim_int_impl!(isize, isize, usize);
[INFO] [stdout]     | ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_leading_trailing_ones)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_reverse_bits`
[INFO] [stdout]    --> src/int.rs:464:19
[INFO] [stdout]     |
[INFO] [stdout] 464 |             #[cfg(has_reverse_bits)]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 510 | prim_int_impl!(isize, isize, usize);
[INFO] [stdout]     | ----------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_reverse_bits)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `prim_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]  --> src/ops/bytes.rs:5:11
[INFO] [stdout]   |
[INFO] [stdout] 5 | #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]   |           ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 321 | int_to_from_bytes_impl!(u8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 321 | int_to_from_bytes_impl!(u8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 321 | int_to_from_bytes_impl!(u8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 321 | int_to_from_bytes_impl!(u8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 322 | int_to_from_bytes_impl!(u16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 322 | int_to_from_bytes_impl!(u16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 322 | int_to_from_bytes_impl!(u16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 322 | int_to_from_bytes_impl!(u16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 323 | int_to_from_bytes_impl!(u32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 323 | int_to_from_bytes_impl!(u32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 323 | int_to_from_bytes_impl!(u32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 323 | int_to_from_bytes_impl!(u32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 324 | int_to_from_bytes_impl!(u64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 324 | int_to_from_bytes_impl!(u64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 324 | int_to_from_bytes_impl!(u64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 324 | int_to_from_bytes_impl!(u64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 325 | int_to_from_bytes_impl!(u128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 325 | int_to_from_bytes_impl!(u128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 325 | int_to_from_bytes_impl!(u128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 325 | int_to_from_bytes_impl!(u128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 327 | int_to_from_bytes_impl!(usize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 327 | int_to_from_bytes_impl!(usize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 327 | int_to_from_bytes_impl!(usize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 327 | int_to_from_bytes_impl!(usize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 331 | int_to_from_bytes_impl!(i8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 331 | int_to_from_bytes_impl!(i8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 331 | int_to_from_bytes_impl!(i8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 331 | int_to_from_bytes_impl!(i8, 1);
[INFO] [stdout]     | ------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 332 | int_to_from_bytes_impl!(i16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 332 | int_to_from_bytes_impl!(i16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 332 | int_to_from_bytes_impl!(i16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 332 | int_to_from_bytes_impl!(i16, 2);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 333 | int_to_from_bytes_impl!(i32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 333 | int_to_from_bytes_impl!(i32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 333 | int_to_from_bytes_impl!(i32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 333 | int_to_from_bytes_impl!(i32, 4);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | int_to_from_bytes_impl!(i64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | int_to_from_bytes_impl!(i64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | int_to_from_bytes_impl!(i64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 334 | int_to_from_bytes_impl!(i64, 8);
[INFO] [stdout]     | ------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 335 | int_to_from_bytes_impl!(i128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 335 | int_to_from_bytes_impl!(i128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 335 | int_to_from_bytes_impl!(i128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 335 | int_to_from_bytes_impl!(i128, 16);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:239:15
[INFO] [stdout]     |
[INFO] [stdout] 239 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | int_to_from_bytes_impl!(isize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:259:15
[INFO] [stdout]     |
[INFO] [stdout] 259 |         #[cfg(has_int_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | int_to_from_bytes_impl!(isize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:279:19
[INFO] [stdout]     |
[INFO] [stdout] 279 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | int_to_from_bytes_impl!(isize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_int_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:299:19
[INFO] [stdout]     |
[INFO] [stdout] 299 |         #[cfg(not(has_int_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 337 | int_to_from_bytes_impl!(isize, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_int_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `int_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:155:15
[INFO] [stdout]     |
[INFO] [stdout] 155 |         #[cfg(has_float_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 341 | float_to_from_bytes_impl!(f32, 4);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:175:15
[INFO] [stdout]     |
[INFO] [stdout] 175 |         #[cfg(has_float_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 341 | float_to_from_bytes_impl!(f32, 4);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:195:19
[INFO] [stdout]     |
[INFO] [stdout] 195 |         #[cfg(not(has_float_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 341 | float_to_from_bytes_impl!(f32, 4);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:215:19
[INFO] [stdout]     |
[INFO] [stdout] 215 |         #[cfg(not(has_float_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 341 | float_to_from_bytes_impl!(f32, 4);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:155:15
[INFO] [stdout]     |
[INFO] [stdout] 155 |         #[cfg(has_float_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 342 | float_to_from_bytes_impl!(f64, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:175:15
[INFO] [stdout]     |
[INFO] [stdout] 175 |         #[cfg(has_float_to_from_bytes)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 342 | float_to_from_bytes_impl!(f64, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:195:19
[INFO] [stdout]     |
[INFO] [stdout] 195 |         #[cfg(not(has_float_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 342 | float_to_from_bytes_impl!(f64, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_float_to_from_bytes`
[INFO] [stdout]    --> src/ops/bytes.rs:215:19
[INFO] [stdout]     |
[INFO] [stdout] 215 |         #[cfg(not(has_float_to_from_bytes))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 342 | float_to_from_bytes_impl!(f64, 8);
[INFO] [stdout]     | --------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_float_to_from_bytes)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `float_to_from_bytes_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:122:11
[INFO] [stdout]     |
[INFO] [stdout] 122 | #[cfg(all(has_div_euclid, feature = "std"))]
[INFO] [stdout]     |           ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:125:15
[INFO] [stdout]     |
[INFO] [stdout] 125 | #[cfg(not(all(has_div_euclid, feature = "std")))]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:147:15
[INFO] [stdout]     |
[INFO] [stdout] 147 | #[cfg(not(all(has_div_euclid, feature = "std")))]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:72:19
[INFO] [stdout]     |
[INFO] [stdout] 72  |         #[cfg(not(has_div_euclid))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 119 | euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 119 | euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 119 | euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 119 | euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 119 | euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 119 | euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 119 | euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | ------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:104:19
[INFO] [stdout]     |
[INFO] [stdout] 104 |         #[cfg(not(has_div_euclid))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 120 | euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 120 | euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 120 | euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 120 | euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 120 | euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 120 | euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 120 | euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | -------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` which comes from the expansion of the macro `euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:53:15
[INFO] [stdout]     |
[INFO] [stdout] 53  |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 123 | euclid_forward_impl!(f32 f64);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `euclid_forward_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:200:19
[INFO] [stdout]     |
[INFO] [stdout] 200 |         #[cfg(not(has_div_euclid))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 250 | checked_euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 250 | checked_euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 250 | checked_euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 250 | checked_euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 250 | checked_euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 250 | checked_euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 250 | checked_euclid_int_impl!(isize i8 i16 i32 i64 i128);
[INFO] [stdout]     | --------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_int_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:227:19
[INFO] [stdout]     |
[INFO] [stdout] 227 |         #[cfg(not(has_div_euclid))]
[INFO] [stdout]     |                   ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 251 | checked_euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 251 | checked_euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 251 | checked_euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 251 | checked_euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 251 | checked_euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 251 | checked_euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: unexpected `cfg` condition name: `has_div_euclid`
[INFO] [stdout]    --> src/ops/euclid.rs:181:15
[INFO] [stdout]     |
[INFO] [stdout] 181 |         #[cfg(has_div_euclid)]
[INFO] [stdout]     |               ^^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 251 | checked_euclid_uint_impl!(usize u8 u16 u32 u64 u128);
[INFO] [stdout]     | ---------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead or adding `println!("cargo:rustc-check-cfg=cfg(has_div_euclid)");` to the top of a `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg> for more information about checking conditional configuration
[INFO] [stdout]     = note: this error originates in the macro `checked_euclid_forward_impl` which comes from the expansion of the macro `checked_euclid_uint_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: aborting due to 133 previous errors
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `num-traits` (lib) due to 134 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] error: aborting due to 133 previous errors
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `num-traits` (lib test) due to 134 previous errors
[INFO] running `Command { std: "docker" "inspect" "2c8770a3686124536bf74aef6c6b9308357691a87c1cf99f97eb6066d898f165", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "2c8770a3686124536bf74aef6c6b9308357691a87c1cf99f97eb6066d898f165", kill_on_drop: false }`
[INFO] [stdout] 2c8770a3686124536bf74aef6c6b9308357691a87c1cf99f97eb6066d898f165
