[INFO] fetching crate completion 0.2.1...
[INFO] checking completion-0.2.1 against try#264a7c4a1c917c83d13895a31231f9d93c7b67e1 for pr-132289
[INFO] extracting crate completion 0.2.1 into /workspace/builds/worker-1-tc2/source
[INFO] validating manifest of crates.io crate completion 0.2.1 on toolchain 264a7c4a1c917c83d13895a31231f9d93c7b67e1
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+264a7c4a1c917c83d13895a31231f9d93c7b67e1" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate completion 0.2.1
[INFO] finished tweaking crates.io crate completion 0.2.1
[INFO] tweaked toml for crates.io crate completion 0.2.1 written to /workspace/builds/worker-1-tc2/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+264a7c4a1c917c83d13895a31231f9d93c7b67e1" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 21 packages to latest compatible versions
[INFO] [stderr]       Adding concurrent-queue v1.2.4 (available: v2.5.0)
[INFO] [stderr]       Adding futures-lite v1.13.0 (available: v2.3.0)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+264a7c4a1c917c83d13895a31231f9d93c7b67e1" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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:4a844ea9eb2546a2d2c7022eacef16ef2e8229c7fbb2c7d4d55a9ceca922f72d" "/opt/rustwide/cargo-home/bin/cargo" "+264a7c4a1c917c83d13895a31231f9d93c7b67e1" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 967f669ecc9fb40ea1a964305ce76509ee3211130167f3fa33e0fb07c82411ef
[INFO] running `Command { std: "docker" "start" "-a" "967f669ecc9fb40ea1a964305ce76509ee3211130167f3fa33e0fb07c82411ef", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "967f669ecc9fb40ea1a964305ce76509ee3211130167f3fa33e0fb07c82411ef", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "967f669ecc9fb40ea1a964305ce76509ee3211130167f3fa33e0fb07c82411ef", kill_on_drop: false }`
[INFO] [stdout] 967f669ecc9fb40ea1a964305ce76509ee3211130167f3fa33e0fb07c82411ef
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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" "-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:4a844ea9eb2546a2d2c7022eacef16ef2e8229c7fbb2c7d4d55a9ceca922f72d" "/opt/rustwide/cargo-home/bin/cargo" "+264a7c4a1c917c83d13895a31231f9d93c7b67e1" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 050e81a8619dbfc9ac229f5cb896b11685350a364fa73be973a0c243a10f3fe8
[INFO] running `Command { std: "docker" "start" "-a" "050e81a8619dbfc9ac229f5cb896b11685350a364fa73be973a0c243a10f3fe8", kill_on_drop: false }`
[INFO] [stderr]     Checking futures-core v0.3.31
[INFO] [stderr]    Compiling syn v1.0.109
[INFO] [stderr]    Compiling completion v0.2.1 (/opt/rustwide/workdir)
[INFO] [stderr]     Checking cache-padded v1.3.0
[INFO] [stderr]     Checking pin-project-lite v0.2.15
[INFO] [stderr]     Checking memchr v2.7.4
[INFO] [stderr]     Checking fastrand v1.9.0
[INFO] [stderr]     Checking futures-io v0.3.31
[INFO] [stderr]     Checking concurrent-queue v1.2.4
[INFO] [stderr]     Checking parking v2.2.1
[INFO] [stderr]     Checking completion-core v0.2.0
[INFO] [stderr]     Checking waker-fn v1.2.0
[INFO] [stderr]     Checking completion-io v0.2.0
[INFO] [stderr]     Checking atomic-waker v1.1.2
[INFO] [stderr]     Checking aliasable v0.1.3
[INFO] [stderr]     Checking futures-lite v1.13.0
[INFO] [stderr]    Compiling completion-macro v0.2.0
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/lib.rs:17:13
[INFO] [stdout]    |
[INFO] [stdout] 17 | #![cfg_attr(doc_cfg, feature(doc_cfg))]
[INFO] [stdout]    |             ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows`
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/lib.rs:67:12
[INFO] [stdout]    |
[INFO] [stdout] 67 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/mod.rs:209:12
[INFO] [stdout]     |
[INFO] [stdout] 209 | #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/mod.rs:214:12
[INFO] [stdout]     |
[INFO] [stdout] 214 | #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/mod.rs:176:16
[INFO] [stdout]     |
[INFO] [stdout] 176 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]     |                ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/block_on.rs:20:12
[INFO] [stdout]    |
[INFO] [stdout] 20 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/zip.rs:35:12
[INFO] [stdout]    |
[INFO] [stdout] 35 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/zip.rs:45:16
[INFO] [stdout]    |
[INFO] [stdout] 45 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |                ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/try_zip.rs:45:12
[INFO] [stdout]    |
[INFO] [stdout] 45 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/try_zip.rs:55:16
[INFO] [stdout]    |
[INFO] [stdout] 55 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |                ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/race.rs:61:12
[INFO] [stdout]    |
[INFO] [stdout] 61 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/race.rs:71:16
[INFO] [stdout]    |
[INFO] [stdout] 71 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |                ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/race_ok.rs:77:12
[INFO] [stdout]    |
[INFO] [stdout] 77 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/race_ok.rs:87:16
[INFO] [stdout]    |
[INFO] [stdout] 87 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |                ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/all/zip.rs:58:12
[INFO] [stdout]    |
[INFO] [stdout] 58 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/all/zip.rs:68:12
[INFO] [stdout]    |
[INFO] [stdout] 68 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/join/all/zip.rs:121:12
[INFO] [stdout]     |
[INFO] [stdout] 121 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/all/try_zip.rs:76:12
[INFO] [stdout]    |
[INFO] [stdout] 76 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/all/try_zip.rs:86:12
[INFO] [stdout]    |
[INFO] [stdout] 86 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/join/all/try_zip.rs:139:12
[INFO] [stdout]     |
[INFO] [stdout] 139 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/all/race.rs:79:12
[INFO] [stdout]    |
[INFO] [stdout] 79 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/all/race.rs:89:12
[INFO] [stdout]    |
[INFO] [stdout] 89 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/join/all/race_ok.rs:114:12
[INFO] [stdout]     |
[INFO] [stdout] 114 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/join/all/race_ok.rs:124:12
[INFO] [stdout]     |
[INFO] [stdout] 124 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/join/all/race_ok.rs:177:12
[INFO] [stdout]     |
[INFO] [stdout] 177 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/mod.rs:114:16
[INFO] [stdout]     |
[INFO] [stdout] 114 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]     |                ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/mod.rs:138:16
[INFO] [stdout]     |
[INFO] [stdout] 138 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]     |                ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/mod.rs:162:16
[INFO] [stdout]     |
[INFO] [stdout] 162 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]     |                ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]     --> src/stream/mod.rs:1148:12
[INFO] [stdout]      |
[INFO] [stdout] 1148 | #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]      |            ^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead
[INFO] [stdout]      = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]               [lints.rust]
[INFO] [stdout]               unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]      = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]     --> src/stream/mod.rs:1153:12
[INFO] [stdout]      |
[INFO] [stdout] 1153 | #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]      |            ^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead
[INFO] [stdout]      = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]               [lints.rust]
[INFO] [stdout]               unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]      = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]     --> src/stream/mod.rs:1189:12
[INFO] [stdout]      |
[INFO] [stdout] 1189 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]      |            ^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead
[INFO] [stdout]      = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]               [lints.rust]
[INFO] [stdout]               unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]      = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]     --> src/stream/mod.rs:1195:12
[INFO] [stdout]      |
[INFO] [stdout] 1195 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]      |            ^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead
[INFO] [stdout]      = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]               [lints.rust]
[INFO] [stdout]               unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]      = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]     --> src/stream/mod.rs:1111:16
[INFO] [stdout]      |
[INFO] [stdout] 1111 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]      |                ^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead
[INFO] [stdout]      = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]               [lints.rust]
[INFO] [stdout]               unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]      = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]     --> src/stream/mod.rs:1136:16
[INFO] [stdout]      |
[INFO] [stdout] 1136 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]      |                ^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead
[INFO] [stdout]      = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]               [lints.rust]
[INFO] [stdout]               unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]      = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/macros/future.rs:81:12
[INFO] [stdout]    |
[INFO] [stdout] 81 | #[cfg_attr(doc_cfg, doc(cfg(all(feature = "macro", feature = "std"))))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/macros/future.rs:135:12
[INFO] [stdout]     |
[INFO] [stdout] 135 | #[cfg_attr(doc_cfg, doc(cfg(all(feature = "macro", feature = "std"))))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/macros/future.rs:161:12
[INFO] [stdout]     |
[INFO] [stdout] 161 | #[cfg_attr(doc_cfg, doc(cfg(all(feature = "macro", feature = "std"))))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/macros/stream.rs:45:12
[INFO] [stdout]    |
[INFO] [stdout] 45 | #[cfg_attr(doc_cfg, doc(cfg(all(feature = "macro", feature = "std"))))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unnecessary qualification
[INFO] [stdout]    --> src/io/buffered/buf_reader.rs:283:9
[INFO] [stdout]     |
[INFO] [stdout] 283 |         std::mem::forget(vec);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: the lint level is defined here
[INFO] [stdout]    --> src/lib.rs:23:5
[INFO] [stdout]     |
[INFO] [stdout] 23  |     unused_qualifications,
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: remove the unnecessary path segments
[INFO] [stdout]     |
[INFO] [stdout] 283 -         std::mem::forget(vec);
[INFO] [stdout] 283 +         mem::forget(vec);
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/lib.rs:17:13
[INFO] [stdout]    |
[INFO] [stdout] 17 | #![cfg_attr(doc_cfg, feature(doc_cfg))]
[INFO] [stdout]    |             ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows`
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/lib.rs:67:12
[INFO] [stdout]    |
[INFO] [stdout] 67 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/mod.rs:209:12
[INFO] [stdout]     |
[INFO] [stdout] 209 | #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/mod.rs:214:12
[INFO] [stdout]     |
[INFO] [stdout] 214 | #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/mod.rs:176:16
[INFO] [stdout]     |
[INFO] [stdout] 176 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]     |                ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/block_on.rs:20:12
[INFO] [stdout]    |
[INFO] [stdout] 20 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/zip.rs:35:12
[INFO] [stdout]    |
[INFO] [stdout] 35 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/zip.rs:45:16
[INFO] [stdout]    |
[INFO] [stdout] 45 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |                ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/try_zip.rs:45:12
[INFO] [stdout]    |
[INFO] [stdout] 45 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/try_zip.rs:55:16
[INFO] [stdout]    |
[INFO] [stdout] 55 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |                ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/race.rs:61:12
[INFO] [stdout]    |
[INFO] [stdout] 61 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/race.rs:71:16
[INFO] [stdout]    |
[INFO] [stdout] 71 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |                ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/race_ok.rs:77:12
[INFO] [stdout]    |
[INFO] [stdout] 77 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/tuple/race_ok.rs:87:16
[INFO] [stdout]    |
[INFO] [stdout] 87 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |                ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/all/zip.rs:58:12
[INFO] [stdout]    |
[INFO] [stdout] 58 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/all/zip.rs:68:12
[INFO] [stdout]    |
[INFO] [stdout] 68 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/join/all/zip.rs:121:12
[INFO] [stdout]     |
[INFO] [stdout] 121 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/all/try_zip.rs:76:12
[INFO] [stdout]    |
[INFO] [stdout] 76 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/all/try_zip.rs:86:12
[INFO] [stdout]    |
[INFO] [stdout] 86 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/join/all/try_zip.rs:139:12
[INFO] [stdout]     |
[INFO] [stdout] 139 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/all/race.rs:79:12
[INFO] [stdout]    |
[INFO] [stdout] 79 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/future/join/all/race.rs:89:12
[INFO] [stdout]    |
[INFO] [stdout] 89 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/join/all/race_ok.rs:114:12
[INFO] [stdout]     |
[INFO] [stdout] 114 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/join/all/race_ok.rs:124:12
[INFO] [stdout]     |
[INFO] [stdout] 124 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/join/all/race_ok.rs:177:12
[INFO] [stdout]     |
[INFO] [stdout] 177 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/mod.rs:114:16
[INFO] [stdout]     |
[INFO] [stdout] 114 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]     |                ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/mod.rs:138:16
[INFO] [stdout]     |
[INFO] [stdout] 138 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]     |                ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/future/mod.rs:162:16
[INFO] [stdout]     |
[INFO] [stdout] 162 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]     |                ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]     --> src/stream/mod.rs:1148:12
[INFO] [stdout]      |
[INFO] [stdout] 1148 | #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]      |            ^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead
[INFO] [stdout]      = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]               [lints.rust]
[INFO] [stdout]               unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]      = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]     --> src/stream/mod.rs:1153:12
[INFO] [stdout]      |
[INFO] [stdout] 1153 | #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]      |            ^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead
[INFO] [stdout]      = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]               [lints.rust]
[INFO] [stdout]               unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]      = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]     --> src/stream/mod.rs:1189:12
[INFO] [stdout]      |
[INFO] [stdout] 1189 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]      |            ^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead
[INFO] [stdout]      = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]               [lints.rust]
[INFO] [stdout]               unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]      = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]     --> src/stream/mod.rs:1195:12
[INFO] [stdout]      |
[INFO] [stdout] 1195 | #[cfg_attr(doc_cfg, doc(cfg(feature = "std")))]
[INFO] [stdout]      |            ^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead
[INFO] [stdout]      = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]               [lints.rust]
[INFO] [stdout]               unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]      = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]     --> src/stream/mod.rs:1111:16
[INFO] [stdout]      |
[INFO] [stdout] 1111 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]      |                ^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead
[INFO] [stdout]      = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]               [lints.rust]
[INFO] [stdout]               unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]      = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]     --> src/stream/mod.rs:1136:16
[INFO] [stdout]      |
[INFO] [stdout] 1136 |     #[cfg_attr(doc_cfg, doc(cfg(feature = "alloc")))]
[INFO] [stdout]      |                ^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = help: consider using a Cargo feature instead
[INFO] [stdout]      = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]               [lints.rust]
[INFO] [stdout]               unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]      = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/macros/future.rs:81:12
[INFO] [stdout]    |
[INFO] [stdout] 81 | #[cfg_attr(doc_cfg, doc(cfg(all(feature = "macro", feature = "std"))))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/macros/future.rs:135:12
[INFO] [stdout]     |
[INFO] [stdout] 135 | #[cfg_attr(doc_cfg, doc(cfg(all(feature = "macro", feature = "std"))))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]    --> src/macros/future.rs:161:12
[INFO] [stdout]     |
[INFO] [stdout] 161 | #[cfg_attr(doc_cfg, doc(cfg(all(feature = "macro", feature = "std"))))]
[INFO] [stdout]     |            ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: lint `box_pointers` has been removed: it does not detect other kinds of allocations, and existed only for historical reasons
[INFO] [stdout]  --> src/macros/future/tests.rs:4:5
[INFO] [stdout]   |
[INFO] [stdout] 4 |     box_pointers,
[INFO] [stdout]   |     ^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout] note: the lint level is defined here
[INFO] [stdout]  --> src/macros/future/tests.rs:1:9
[INFO] [stdout]   |
[INFO] [stdout] 1 | #![deny(warnings)]
[INFO] [stdout]   |         ^^^^^^^^
[INFO] [stdout]   = note: `#[deny(renamed_and_removed_lints)]` implied by `#[deny(warnings)]`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: lint `pointer_structural_match` has been removed: converted into hard error, see RFC #3535 <https://rust-lang.github.io/rfcs/3535-constants-in-patterns.html> for more information
[INFO] [stdout]   --> src/macros/future/tests.rs:14:5
[INFO] [stdout]    |
[INFO] [stdout] 14 |     pointer_structural_match,
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: lint `unaligned_references` has been removed: converted into hard error, see issue #82523 <https://github.com/rust-lang/rust/issues/82523> for more information
[INFO] [stdout]   --> src/macros/future/tests.rs:19:5
[INFO] [stdout]    |
[INFO] [stdout] 19 |     unaligned_references,
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `doc_cfg`
[INFO] [stdout]   --> src/macros/stream.rs:45:12
[INFO] [stdout]    |
[INFO] [stdout] 45 | #[cfg_attr(doc_cfg, doc(cfg(all(feature = "macro", feature = "std"))))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(doc_cfg)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(doc_cfg)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: lint `box_pointers` has been removed: it does not detect other kinds of allocations, and existed only for historical reasons
[INFO] [stdout]  --> src/macros/stream/tests.rs:4:5
[INFO] [stdout]   |
[INFO] [stdout] 4 |     box_pointers,
[INFO] [stdout]   |     ^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout] note: the lint level is defined here
[INFO] [stdout]  --> src/macros/stream/tests.rs:1:9
[INFO] [stdout]   |
[INFO] [stdout] 1 | #![deny(warnings)]
[INFO] [stdout]   |         ^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: lint `pointer_structural_match` has been removed: converted into hard error, see RFC #3535 <https://rust-lang.github.io/rfcs/3535-constants-in-patterns.html> for more information
[INFO] [stdout]   --> src/macros/stream/tests.rs:14:5
[INFO] [stdout]    |
[INFO] [stdout] 14 |     pointer_structural_match,
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: lint `unaligned_references` has been removed: converted into hard error, see issue #82523 <https://github.com/rust-lang/rust/issues/82523> for more information
[INFO] [stdout]   --> src/macros/stream/tests.rs:19:5
[INFO] [stdout]    |
[INFO] [stdout] 19 |     unaligned_references,
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unnecessary qualification
[INFO] [stdout]    --> src/io/buffered/buf_reader.rs:283:9
[INFO] [stdout]     |
[INFO] [stdout] 283 |         std::mem::forget(vec);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: the lint level is defined here
[INFO] [stdout]    --> src/lib.rs:23:5
[INFO] [stdout]     |
[INFO] [stdout] 23  |     unused_qualifications,
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: remove the unnecessary path segments
[INFO] [stdout]     |
[INFO] [stdout] 283 -         std::mem::forget(vec);
[INFO] [stdout] 283 +         mem::forget(vec);
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: lint `box_pointers` has been removed: it does not detect other kinds of allocations, and existed only for historical reasons
[INFO] [stdout]  --> tests/hygiene.rs:5:5
[INFO] [stdout]   |
[INFO] [stdout] 5 |     box_pointers,
[INFO] [stdout]   |     ^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout] note: the lint level is defined here
[INFO] [stdout]  --> tests/hygiene.rs:2:9
[INFO] [stdout]   |
[INFO] [stdout] 2 | #![deny(warnings)]
[INFO] [stdout]   |         ^^^^^^^^
[INFO] [stdout]   = note: `#[deny(renamed_and_removed_lints)]` implied by `#[deny(warnings)]`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: lint `pointer_structural_match` has been removed: converted into hard error, see RFC #3535 <https://rust-lang.github.io/rfcs/3535-constants-in-patterns.html> for more information
[INFO] [stdout]   --> tests/hygiene.rs:17:5
[INFO] [stdout]    |
[INFO] [stdout] 17 |     pointer_structural_match,
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: lint `unaligned_references` has been removed: converted into hard error, see issue #82523 <https://github.com/rust-lang/rust/issues/82523> for more information
[INFO] [stdout]   --> tests/hygiene.rs:22:5
[INFO] [stdout]    |
[INFO] [stdout] 22 |     unaligned_references,
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: missing documentation for the crate
[INFO] [stdout]   --> tests/hygiene.rs:1:1
[INFO] [stdout]    |
[INFO] [stdout] 1  | / #![cfg(all(feature = "macro", feature = "std"))]
[INFO] [stdout] 2  | | #![deny(warnings)]
[INFO] [stdout] 3  | | #![deny(
[INFO] [stdout] 4  | |     absolute_paths_not_starting_with_crate,
[INFO] [stdout] ...  |
[INFO] [stdout] 53 | |     };
[INFO] [stdout] 54 | | }
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout] note: the lint level is defined here
[INFO] [stdout]   --> tests/hygiene.rs:15:5
[INFO] [stdout]    |
[INFO] [stdout] 15 |     missing_docs,
[INFO] [stdout]    |     ^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `completion` (test "hygiene") due to 4 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 345 |     ($($param:ident),*) => { const _: () = {
[INFO] [stdout]     |                              ----------- move the `impl` block outside of this constant `_` and up 2 bodies
[INFO] [stdout] ...
[INFO] [stdout] 353 |         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^---------^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  `JoinTuple` is not local
[INFO] [stdout] ...
[INFO] [stdout] 434 | apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     | ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: the macro `impl_tuple` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]     = note: this warning originates in the macro `impl_tuple` which comes from the expansion of the macro `apply_on_tuples` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `completion` (lib test) due to 6 previous errors; 64 warnings emitted
[INFO] running `Command { std: "docker" "inspect" "050e81a8619dbfc9ac229f5cb896b11685350a364fa73be973a0c243a10f3fe8", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "050e81a8619dbfc9ac229f5cb896b11685350a364fa73be973a0c243a10f3fe8", kill_on_drop: false }`
[INFO] [stdout] 050e81a8619dbfc9ac229f5cb896b11685350a364fa73be973a0c243a10f3fe8
