[INFO] fetching crate completion 0.2.1...
[INFO] checking completion-0.2.1 against master#c2f2db79ca3024f68d22b45aa22b570775c2c4ad for pr-124157
[INFO] extracting crate completion 0.2.1 into /workspace/builds/worker-6-tc1/source
[INFO] validating manifest of crates.io crate completion 0.2.1 on toolchain c2f2db79ca3024f68d22b45aa22b570775c2c4ad
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+c2f2db79ca3024f68d22b45aa22b570775c2c4ad" "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-6-tc1/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+c2f2db79ca3024f68d22b45aa22b570775c2c4ad" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 22 packages to latest compatible versions
[INFO] [stderr]       Adding concurrent-queue v1.2.4 (latest: v2.5.0)
[INFO] [stderr]       Adding fastrand v1.9.0 (latest: v2.1.0)
[INFO] [stderr]       Adding futures-lite v1.13.0 (latest: v2.3.0)
[INFO] [stderr]       Adding syn v1.0.109 (latest: v2.0.60)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+c2f2db79ca3024f68d22b45aa22b570775c2c4ad" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded aliasable v0.1.3
[INFO] [stderr]   Downloaded completion-core v0.2.0
[INFO] [stderr]   Downloaded completion-macro v0.2.0
[INFO] [stderr]   Downloaded completion-io v0.2.0
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:99613afd962a8cfa530ec1899472a458bd015a1ab0af876cf7eb06f6006d81ea" "/opt/rustwide/cargo-home/bin/cargo" "+c2f2db79ca3024f68d22b45aa22b570775c2c4ad" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 00b09b4cf9408b4b7fb3c49292f5fbf19ea2a3500c3c57acf007d485f43e37ab
[INFO] running `Command { std: "docker" "start" "-a" "00b09b4cf9408b4b7fb3c49292f5fbf19ea2a3500c3c57acf007d485f43e37ab", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "00b09b4cf9408b4b7fb3c49292f5fbf19ea2a3500c3c57acf007d485f43e37ab", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "00b09b4cf9408b4b7fb3c49292f5fbf19ea2a3500c3c57acf007d485f43e37ab", kill_on_drop: false }`
[INFO] [stdout] 00b09b4cf9408b4b7fb3c49292f5fbf19ea2a3500c3c57acf007d485f43e37ab
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:99613afd962a8cfa530ec1899472a458bd015a1ab0af876cf7eb06f6006d81ea" "/opt/rustwide/cargo-home/bin/cargo" "+c2f2db79ca3024f68d22b45aa22b570775c2c4ad" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 09694ed4b6d0303c86603c7e4633e352d8dc12189cffcad0e06461477c6ab8ce
[INFO] running `Command { std: "docker" "start" "-a" "09694ed4b6d0303c86603c7e4633e352d8dc12189cffcad0e06461477c6ab8ce", kill_on_drop: false }`
[INFO] [stderr]    Compiling syn v1.0.109
[INFO] [stderr]     Checking cache-padded v1.3.0
[INFO] [stderr]    Compiling completion v0.2.1 (/opt/rustwide/workdir)
[INFO] [stderr]     Checking aliasable v0.1.3
[INFO] [stderr]     Checking atomic-waker v1.1.2
[INFO] [stderr]     Checking completion-core v0.2.0
[INFO] [stderr]     Checking concurrent-queue v1.2.4
[INFO] [stderr]     Checking completion-io v0.2.0
[INFO] [stderr]    Compiling completion-macro v0.2.0
[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] 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] 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 `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] 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] 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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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: 26 warnings emitted
[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] 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: aborting due to 1 previous error
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `completion` (test "hygiene") due to 2 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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: aborting due to 2 previous errors; 26 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `completion` (lib test) due to 3 previous errors; 26 warnings emitted
[INFO] running `Command { std: "docker" "inspect" "09694ed4b6d0303c86603c7e4633e352d8dc12189cffcad0e06461477c6ab8ce", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "09694ed4b6d0303c86603c7e4633e352d8dc12189cffcad0e06461477c6ab8ce", kill_on_drop: false }`
[INFO] [stdout] 09694ed4b6d0303c86603c7e4633e352d8dc12189cffcad0e06461477c6ab8ce
[INFO] checking completion-0.2.1 against try#9c7b5f5b6b8ec32bbbcf9f07fc0e5208da6c5f88 for pr-124157
[INFO] extracting crate completion 0.2.1 into /workspace/builds/worker-6-tc2/source
[INFO] validating manifest of crates.io crate completion 0.2.1 on toolchain 9c7b5f5b6b8ec32bbbcf9f07fc0e5208da6c5f88
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+9c7b5f5b6b8ec32bbbcf9f07fc0e5208da6c5f88" "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-6-tc2/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+9c7b5f5b6b8ec32bbbcf9f07fc0e5208da6c5f88" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 22 packages to latest compatible versions
[INFO] [stderr]       Adding concurrent-queue v1.2.4 (latest: v2.5.0)
[INFO] [stderr]       Adding fastrand v1.9.0 (latest: v2.1.0)
[INFO] [stderr]       Adding futures-lite v1.13.0 (latest: v2.3.0)
[INFO] [stderr]       Adding syn v1.0.109 (latest: v2.0.60)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+9c7b5f5b6b8ec32bbbcf9f07fc0e5208da6c5f88" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:99613afd962a8cfa530ec1899472a458bd015a1ab0af876cf7eb06f6006d81ea" "/opt/rustwide/cargo-home/bin/cargo" "+9c7b5f5b6b8ec32bbbcf9f07fc0e5208da6c5f88" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] a9577f51eeab6d49b5a975ea1088c2e9d9b5a9583cc524624f1228cff857c6ca
[INFO] running `Command { std: "docker" "start" "-a" "a9577f51eeab6d49b5a975ea1088c2e9d9b5a9583cc524624f1228cff857c6ca", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "a9577f51eeab6d49b5a975ea1088c2e9d9b5a9583cc524624f1228cff857c6ca", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "a9577f51eeab6d49b5a975ea1088c2e9d9b5a9583cc524624f1228cff857c6ca", kill_on_drop: false }`
[INFO] [stdout] a9577f51eeab6d49b5a975ea1088c2e9d9b5a9583cc524624f1228cff857c6ca
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-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:99613afd962a8cfa530ec1899472a458bd015a1ab0af876cf7eb06f6006d81ea" "/opt/rustwide/cargo-home/bin/cargo" "+9c7b5f5b6b8ec32bbbcf9f07fc0e5208da6c5f88" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 64e32fc1f0340bb620ee104ed2e1d7a8c4e60d1ab15e1be265db549c5005d6bb
[INFO] running `Command { std: "docker" "start" "-a" "64e32fc1f0340bb620ee104ed2e1d7a8c4e60d1ab15e1be265db549c5005d6bb", kill_on_drop: false }`
[INFO] [stderr]    Compiling syn v1.0.109
[INFO] [stderr]     Checking cache-padded v1.3.0
[INFO] [stderr]    Compiling completion v0.2.1 (/opt/rustwide/workdir)
[INFO] [stderr]     Checking completion-core v0.2.0
[INFO] [stderr]     Checking atomic-waker v1.1.2
[INFO] [stderr]     Checking aliasable v0.1.3
[INFO] [stderr]     Checking concurrent-queue v1.2.4
[INFO] [stderr]     Checking completion-io v0.2.0
[INFO] [stderr]    Compiling completion-macro v0.2.0
[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] 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] 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 `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] 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] 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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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: 26 warnings emitted
[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] 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: aborting due to 1 previous error
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `completion` (test "hygiene") due to 2 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] warning: non-local `impl` definition, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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, they should be avoided as they go against expectation
[INFO] [stdout]    --> src/future/join/tuple/base.rs:353:9
[INFO] [stdout]     |
[INFO] [stdout] 353 | /         impl<Break, $($param,)*> JoinTuple for ($($param,)*)
[INFO] [stdout] 354 | |         where
[INFO] [stdout] 355 | |             $($param: ControlFlowFuture<Break = Break>,)*
[INFO] [stdout] 356 | |         {
[INFO] [stdout] ...   |
[INFO] [stdout] 430 | |             }
[INFO] [stdout] 431 | |         }
[INFO] [stdout]     | |_________^
[INFO] [stdout] ...
[INFO] [stdout] 434 |   apply_on_tuples!(impl_tuple!);
[INFO] [stdout]     |   ----------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: move this `impl` block outside the of the current constant `_` and up 2 bodies
[INFO] [stdout]     = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
[INFO] [stdout]     = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
[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: aborting due to 2 previous errors; 26 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `completion` (lib test) due to 3 previous errors; 26 warnings emitted
[INFO] running `Command { std: "docker" "inspect" "64e32fc1f0340bb620ee104ed2e1d7a8c4e60d1ab15e1be265db549c5005d6bb", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "64e32fc1f0340bb620ee104ed2e1d7a8c4e60d1ab15e1be265db549c5005d6bb", kill_on_drop: false }`
[INFO] [stdout] 64e32fc1f0340bb620ee104ed2e1d7a8c4e60d1ab15e1be265db549c5005d6bb
