[INFO] fetching crate async-task-ffi 4.1.1...
[INFO] checking async-task-ffi-4.1.1 against try#a7a572ce3edd6d476191fbfe92c9c1986e009b34 for pr-87190-3
[INFO] extracting crate async-task-ffi 4.1.1 into /workspace/builds/worker-87/source
[INFO] validating manifest of crates.io crate async-task-ffi 4.1.1 on toolchain a7a572ce3edd6d476191fbfe92c9c1986e009b34
[INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+a7a572ce3edd6d476191fbfe92c9c1986e009b34" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate async-task-ffi 4.1.1
[INFO] finished tweaking crates.io crate async-task-ffi 4.1.1
[INFO] tweaked toml for crates.io crate async-task-ffi 4.1.1 written to /workspace/builds/worker-87/source/Cargo.toml
[INFO] crate crates.io crate async-task-ffi 4.1.1 already has a lockfile, it will not be regenerated
[INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+a7a572ce3edd6d476191fbfe92c9c1986e009b34" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded flume v0.10.1
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-87/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-87/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:34b6a614d2c27851fe6cbf88fbd1137609cefab8b10d0615aaeb6fd47975d74e" "/opt/rustwide/cargo-home/bin/cargo" "+a7a572ce3edd6d476191fbfe92c9c1986e009b34" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 7bd91e1606a34b6e1e5ca4d4a02b07a0ec844b8f5f07adbe5a32a219a7c54575
[INFO] running `Command { std: "docker" "start" "-a" "7bd91e1606a34b6e1e5ca4d4a02b07a0ec844b8f5f07adbe5a32a219a7c54575", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "7bd91e1606a34b6e1e5ca4d4a02b07a0ec844b8f5f07adbe5a32a219a7c54575", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "7bd91e1606a34b6e1e5ca4d4a02b07a0ec844b8f5f07adbe5a32a219a7c54575", kill_on_drop: false }`
[INFO] [stdout] 7bd91e1606a34b6e1e5ca4d4a02b07a0ec844b8f5f07adbe5a32a219a7c54575
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-87/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-87/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" "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:34b6a614d2c27851fe6cbf88fbd1137609cefab8b10d0615aaeb6fd47975d74e" "/opt/rustwide/cargo-home/bin/cargo" "+a7a572ce3edd6d476191fbfe92c9c1986e009b34" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 6f307c4e7774a250ca637b42c83b615662f5f1c162ade611b7cd764de1d5d54b
[INFO] running `Command { std: "docker" "start" "-a" "6f307c4e7774a250ca637b42c83b615662f5f1c162ade611b7cd764de1d5d54b", kill_on_drop: false }`
[INFO] [stderr] Copying to /tmp/fixit
[INFO] [stderr] Running `cargo fix --edition`
[INFO] [stderr]    Compiling memchr v2.3.4
[INFO] [stderr]    Compiling libc v0.2.82
[INFO] [stderr]     Checking cache-padded v1.1.1
[INFO] [stderr]     Checking futures-core v0.3.12
[INFO] [stderr]     Checking pin-project-lite v0.2.4
[INFO] [stderr]     Checking fastrand v1.4.0
[INFO] [stderr]     Checking waker-fn v1.1.0
[INFO] [stderr]     Checking parking v2.0.0
[INFO] [stderr]     Checking futures-io v0.3.12
[INFO] [stderr]    Compiling log v0.4.13
[INFO] [stderr]     Checking once_cell v1.5.2
[INFO] [stderr]     Checking event-listener v2.5.1
[INFO] [stderr]     Checking vec-arena v1.0.0
[INFO] [stderr]     Checking async-task v4.0.3
[INFO] [stderr]     Checking atomic-waker v1.0.0
[INFO] [stderr]     Checking easy-parallel v3.1.0
[INFO] [stderr]     Checking async-task-ffi v4.1.1 (/tmp/fixit)
[INFO] [stderr]     Checking lock_api v0.4.2
[INFO] [stderr]    Migrating src/lib.rs from 2018 edition to 2021
[INFO] [stderr]     Checking async-lock v2.3.0
[INFO] [stderr]     Checking concurrent-queue v1.2.2
[INFO] [stderr]     Checking spinning_top v0.2.2
[INFO] [stderr]     Checking flume v0.10.1
[INFO] [stderr]     Checking async-channel v1.5.1
[INFO] [stderr]     Checking futures-lite v1.11.3
[INFO] [stderr]     Checking polling v2.0.2
[INFO] [stderr]     Checking nb-connect v1.0.2
[INFO] [stderr]     Checking signal-hook-registry v1.3.0
[INFO] [stderr]     Checking signal-hook v0.1.17
[INFO] [stderr]     Checking blocking v1.0.2
[INFO] [stderr]     Checking async-io v1.3.1
[INFO] [stderr]     Checking async-executor v1.4.0
[INFO] [stderr]     Checking async-fs v1.5.0
[INFO] [stderr]     Checking async-net v1.5.0
[INFO] [stderr]     Checking async-process v1.0.1
[INFO] [stderr]     Checking smol v1.2.5
[INFO] [stderr]    Migrating examples/spawn-local.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/waker_ready.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/waker_panic.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating benches/spawn.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating examples/spawn.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating examples/spawn-on-thread.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/join.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/ready.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/panic.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/waker_pending.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/basic.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/cancel.rs from 2018 edition to 2021
[INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `waker_ready`
[INFO] [stderr] 
[INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files:
[INFO] [stderr] 
[INFO] [stderr]   * tests/waker_ready.rs
[INFO] [stderr] 
[INFO] [stderr] This likely indicates a bug in either rustc or cargo itself,
[INFO] [stderr] and we would appreciate a bug report! You're likely to see 
[INFO] [stderr] a number of compiler warnings after this message which cargo
[INFO] [stderr] attempted to fix but failed. If you could open an issue at
[INFO] [stderr] https://github.com/rust-lang/rust/issues
[INFO] [stderr] quoting the full output of this command we'd be very appreciative!
[INFO] [stderr] Note that you may be able to make some more progress in the near-term
[INFO] [stderr] fixing code with the `--broken-code` flag
[INFO] [stderr] 
[INFO] [stderr] The following errors were reported:
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_ready.rs:97:25
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 117 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_ready.rs:97:25
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 159 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_ready.rs:97:25
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 202 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_ready.rs:97:25
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 245 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_ready.rs:97:25
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 280 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:49
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 117 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:41
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 117 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:33
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 117 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:25
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 117 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:49
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 159 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:41
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 159 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:33
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 159 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:25
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 159 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:49
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 202 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:41
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 202 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:33
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 202 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:25
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 202 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:49
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 245 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:41
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 245 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:33
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 245 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:25
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 245 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:49
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 280 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:41
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 280 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:33
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 280 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_ready.rs:97:25
[INFO] [stderr]     |
[INFO] [stderr] 97  |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 280 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to 25 previous errors
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0658`.
[INFO] [stderr] Original diagnostics will follow.
[INFO] [stderr] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_ready.rs:97:17
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 117 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_ready.rs:97:17
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 159 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_ready.rs:97:17
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 202 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_ready.rs:97:17
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 245 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_ready.rs:97:17
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 280 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 5 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `ready`
[INFO] [stderr] 
[INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files:
[INFO] [stderr] 
[INFO] [stderr]   * tests/ready.rs
[INFO] [stderr] 
[INFO] [stderr] This likely indicates a bug in either rustc or cargo itself,
[INFO] [stderr] and we would appreciate a bug report! You're likely to see 
[INFO] [stderr] a number of compiler warnings after this message which cargo
[INFO] [stderr] attempted to fix but failed. If you could open an issue at
[INFO] [stderr] https://github.com/rust-lang/rust/issues
[INFO] [stderr] quoting the full output of this command we'd be very appreciative!
[INFO] [stderr] Note that you may be able to make some more progress in the near-term
[INFO] [stderr] fixing code with the `--broken-code` flag
[INFO] [stderr] 
[INFO] [stderr] The following errors were reported:
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/ready.rs:95:25
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 114 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/ready.rs:95:25
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 160 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/ready.rs:95:25
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 195 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/ready.rs:95:25
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 226 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/ready.rs:95:41
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 114 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/ready.rs:95:33
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 114 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/ready.rs:95:25
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 114 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/ready.rs:95:41
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 160 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/ready.rs:95:33
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 160 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/ready.rs:95:25
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 160 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/ready.rs:95:41
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 195 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/ready.rs:95:33
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 195 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/ready.rs:95:25
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 195 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/ready.rs:95:41
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 226 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/ready.rs:95:33
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 226 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/ready.rs:95:25
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 226 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to 16 previous errors
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0658`.
[INFO] [stderr] Original diagnostics will follow.
[INFO] [stderr] 
[INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `join`
[INFO] [stderr] 
[INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files:
[INFO] [stderr] 
[INFO] [stderr]   * tests/join.rs
[INFO] [stderr] 
[INFO] [stderr] This likely indicates a bug in either rustc or cargo itself,
[INFO] [stderr] and we would appreciate a bug report! You're likely to see 
[INFO] [stderr] a number of compiler warnings after this message which cargo
[INFO] [stderr] attempted to fix but failed. If you could open an issue at
[INFO] [stderr] https://github.com/rust-lang/rust/issues
[INFO] [stderr] quoting the full output of this command we'd be very appreciative!
[INFO] [stderr] Note that you may be able to make some more progress in the near-term
[INFO] [stderr] fixing code with the `--broken-code` flag
[INFO] [stderr] 
[INFO] [stderr] The following errors were reported:
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 117 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 138 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 159 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 180 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 214 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 247 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 280 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 322 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 359 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:81
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 117 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:73
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 117 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:65
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 117 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:57
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 117 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:49
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 117 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:41
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 117 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:33
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 117 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 117 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:81
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 138 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:73
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 138 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:65
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 138 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:57
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 138 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:49
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 138 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:41
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 138 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:33
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 138 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 138 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:81
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 159 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:73
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 159 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:65
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 159 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:57
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 159 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:49
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 159 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:41
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 159 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:33
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 159 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 159 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:81
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 180 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:73
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 180 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:65
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 180 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:57
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 180 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:49
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 180 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:41
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 180 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:33
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 180 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 180 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:81
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 214 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:73
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 214 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:65
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 214 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:57
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 214 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:49
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 214 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:41
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 214 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:33
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 214 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 214 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:81
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 247 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:73
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 247 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:65
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 247 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:57
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 247 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:49
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 247 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:41
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 247 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:33
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 247 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 247 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:81
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 280 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:73
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 280 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:65
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 280 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:57
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 280 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:49
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 280 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:41
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 280 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:33
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 280 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 280 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:81
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 322 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:73
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 322 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:65
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 322 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:57
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 322 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:49
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 322 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:41
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 322 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:33
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 322 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 322 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:81
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 359 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:73
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 359 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:65
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 359 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:57
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 359 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:49
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 359 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:41
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 359 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:33
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 359 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/join.rs:96:25
[INFO] [stderr]     |
[INFO] [stderr] 96  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 359 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to 81 previous errors
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0658`.
[INFO] [stderr] Original diagnostics will follow.
[INFO] [stderr] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/ready.rs:95:17
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 114 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/ready.rs:95:17
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 160 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/ready.rs:95:17
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 195 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/ready.rs:95:17
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 226 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 4 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `panic`
[INFO] [stderr] 
[INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files:
[INFO] [stderr] 
[INFO] [stderr]   * tests/panic.rs
[INFO] [stderr] 
[INFO] [stderr] This likely indicates a bug in either rustc or cargo itself,
[INFO] [stderr] and we would appreciate a bug report! You're likely to see 
[INFO] [stderr] a number of compiler warnings after this message which cargo
[INFO] [stderr] attempted to fix but failed. If you could open an issue at
[INFO] [stderr] https://github.com/rust-lang/rust/issues
[INFO] [stderr] quoting the full output of this command we'd be very appreciative!
[INFO] [stderr] Note that you may be able to make some more progress in the near-term
[INFO] [stderr] fixing code with the `--broken-code` flag
[INFO] [stderr] 
[INFO] [stderr] The following errors were reported:
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/panic.rs:83:25
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 102 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/panic.rs:83:25
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 130 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/panic.rs:83:25
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 151 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/panic.rs:83:25
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 179 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/panic.rs:83:25
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 211 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/panic.rs:83:25
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 241 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:57
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 102 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:49
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 102 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:41
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 102 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:33
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 102 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:25
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 102 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:57
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 130 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:49
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 130 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:41
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 130 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:33
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 130 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:25
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 130 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:57
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 151 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:49
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 151 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:41
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 151 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:33
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 151 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:25
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 151 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:57
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 179 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:49
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 179 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:41
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 179 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:33
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 179 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:25
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 179 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:57
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 211 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:49
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 211 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:41
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 211 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:33
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 211 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:25
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 211 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:57
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 241 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:49
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 241 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:41
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 241 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:33
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 241 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/panic.rs:83:25
[INFO] [stderr]     |
[INFO] [stderr] 83  |                 let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 241 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to 36 previous errors
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0658`.
[INFO] [stderr] Original diagnostics will follow.
[INFO] [stderr] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 117 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 138 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 159 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 180 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 214 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 247 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 280 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 322 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 359 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 9 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/panic.rs:83:17
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 102 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/panic.rs:83:17
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 130 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/panic.rs:83:17
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 151 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/panic.rs:83:17
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 179 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/panic.rs:83:17
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 211 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/panic.rs:83:17
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 241 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 6 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `waker_panic`
[INFO] [stderr] 
[INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files:
[INFO] [stderr] 
[INFO] [stderr]   * tests/waker_panic.rs
[INFO] [stderr] 
[INFO] [stderr] This likely indicates a bug in either rustc or cargo itself,
[INFO] [stderr] and we would appreciate a bug report! You're likely to see 
[INFO] [stderr] a number of compiler warnings after this message which cargo
[INFO] [stderr] attempted to fix but failed. If you could open an issue at
[INFO] [stderr] https://github.com/rust-lang/rust/issues
[INFO] [stderr] quoting the full output of this command we'd be very appreciative!
[INFO] [stderr] Note that you may be able to make some more progress in the near-term
[INFO] [stderr] fixing code with the `--broken-code` flag
[INFO] [stderr] 
[INFO] [stderr] The following errors were reported:
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_panic.rs:100:25
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 124 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_panic.rs:100:25
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 170 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_panic.rs:100:25
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 215 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_panic.rs:100:25
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 268 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_panic.rs:100:25
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 321 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:49
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 124 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:41
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 124 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:33
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 124 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:25
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 124 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:49
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 170 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:41
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 170 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:33
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 170 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:25
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 170 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:49
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 215 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:41
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 215 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:33
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 215 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:25
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 215 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:49
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 268 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:41
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 268 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:33
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 268 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:25
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 268 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:49
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 321 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:41
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 321 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:33
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 321 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_panic.rs:100:25
[INFO] [stderr]     |
[INFO] [stderr] 100 |                 let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 321 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to 25 previous errors
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0658`.
[INFO] [stderr] Original diagnostics will follow.
[INFO] [stderr] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_panic.rs:100:17
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 124 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_panic.rs:100:17
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 170 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_panic.rs:100:17
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 215 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `waker_pending`
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_panic.rs:100:17
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 268 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] 
[INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files:
[INFO] [stderr] 
[INFO] [stderr]   * tests/waker_pending.rs
[INFO] [stderr] 
[INFO] [stderr] This likely indicates a bug in either rustc or cargo itself,
[INFO] [stderr] and we would appreciate a bug report! You're likely to see 
[INFO] [stderr] a number of compiler warnings after this message which cargo
[INFO] [stderr] attempted to fix but failed. If you could open an issue at
[INFO] [stderr] https://github.com/rust-lang/rust/issues
[INFO] [stderr] quoting the full output of this command we'd be very appreciative!
[INFO] [stderr] Note that you may be able to make some more progress in the near-term
[INFO] [stderr] fixing code with the `--broken-code` flag
[INFO] [stderr] 
[INFO] [stderr] The following errors were reported:
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_pending.rs:91:25
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 111 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_pending.rs:91:25
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 158 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_pending.rs:91:25
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 203 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_pending.rs:91:25
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 256 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_pending.rs:91:25
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 309 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_pending.rs:91:25
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 343 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/waker_pending.rs:91:25
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 375 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:65
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 111 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:57
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 111 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:49
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 111 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:41
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 111 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:33
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 111 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:25
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 111 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:65
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 158 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:57
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 158 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:49
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 158 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:41
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 158 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:33
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 158 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:25
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 158 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:65
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 203 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:57
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 203 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:49
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 203 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:41
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 203 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:33
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 203 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:25
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 203 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:65
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 256 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_panic.rs:100:17
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 321 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:57
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 256 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:49
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 256 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:41
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 256 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:33
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 256 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:25
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 256 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:65
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 309 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:57
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 309 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:49
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 309 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:41
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 309 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:33
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 309 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:25
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 309 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:65
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 343 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:57
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 343 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:49
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 343 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:41
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 343 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:33
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 343 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:25
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 343 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:65
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 375 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:57
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 375 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:49
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 375 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:41
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 375 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:33
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 375 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/waker_pending.rs:91:25
[INFO] [stderr]     |
[INFO] [stderr] 91  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 375 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to 49 previous errors
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0658`.
[INFO] [stderr] Original diagnostics will follow.
[INFO] [stderr] 
[INFO] [stdout] warning: 5 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `basic`
[INFO] [stderr] 
[INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files:
[INFO] [stderr] 
[INFO] [stderr]   * tests/basic.rs
[INFO] [stderr] 
[INFO] [stderr] This likely indicates a bug in either rustc or cargo itself,
[INFO] [stderr] and we would appreciate a bug report! You're likely to see 
[INFO] [stderr] a number of compiler warnings after this message which cargo
[INFO] [stderr] attempted to fix but failed. If you could open an issue at
[INFO] [stderr] https://github.com/rust-lang/rust/issues
[INFO] [stderr] quoting the full output of this command we'd be very appreciative!
[INFO] [stderr] Note that you may be able to make some more progress in the near-term
[INFO] [stderr] fixing code with the `--broken-code` flag
[INFO] [stderr] 
[INFO] [stderr] The following errors were reported:
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]   --> tests/basic.rs:78:25
[INFO] [stderr]    |
[INFO] [stderr] 78 |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]    |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 97 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]    |     ---------------------------------------- in this macro invocation
[INFO] [stderr]    |
[INFO] [stderr]    = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]    = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]    = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/basic.rs:78:25
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 124 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/basic.rs:78:25
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 145 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/basic.rs:78:25
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 166 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/basic.rs:78:25
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 187 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/basic.rs:78:25
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/basic.rs:78:25
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 229 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]   --> tests/basic.rs:78:65
[INFO] [stderr]    |
[INFO] [stderr] 78 |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]    |                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 97 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]    |     ---------------------------------------- in this macro invocation
[INFO] [stderr]    |
[INFO] [stderr]    = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]    = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]    = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]    = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]   --> tests/basic.rs:78:57
[INFO] [stderr]    |
[INFO] [stderr] 78 |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]    |                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 97 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]    |     ---------------------------------------- in this macro invocation
[INFO] [stderr]    |
[INFO] [stderr]    = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]    = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]    = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]    = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]   --> tests/basic.rs:78:49
[INFO] [stderr]    |
[INFO] [stderr] 78 |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]    |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 97 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]    |     ---------------------------------------- in this macro invocation
[INFO] [stderr]    |
[INFO] [stderr]    = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]    = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]    = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]    = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]   --> tests/basic.rs:78:41
[INFO] [stderr]    |
[INFO] [stderr] 78 |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]    |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 97 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]    |     ---------------------------------------- in this macro invocation
[INFO] [stderr]    |
[INFO] [stderr]    = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]    = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]    = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]    = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]   --> tests/basic.rs:78:33
[INFO] [stderr]    |
[INFO] [stderr] 78 |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 97 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]    |     ---------------------------------------- in this macro invocation
[INFO] [stderr]    |
[INFO] [stderr]    = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]    = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]    = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]    = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]   --> tests/basic.rs:78:25
[INFO] [stderr]    |
[INFO] [stderr] 78 |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]    |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 97 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]    |     ---------------------------------------- in this macro invocation
[INFO] [stderr]    |
[INFO] [stderr]    = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]    = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]    = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]    = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:65
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 124 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:57
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 124 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:49
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 124 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:41
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 124 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:33
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 124 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:25
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 124 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:65
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 145 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:57
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 145 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:49
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 145 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:41
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 145 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:33
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 145 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:25
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 145 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:65
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 166 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:57
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 166 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:49
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 166 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:41
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 166 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:33
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 166 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:25
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 166 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:65
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 187 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:57
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 187 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:49
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 187 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:41
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 187 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:33
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 187 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:25
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 187 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:65
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:57
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:49
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:41
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:33
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:25
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 208 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:65
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 229 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:57
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 229 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:49
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 229 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:41
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 229 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:33
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 229 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/basic.rs:78:25
[INFO] [stderr]     |
[INFO] [stderr] 78  |                 let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 229 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to 49 previous errors
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0658`.
[INFO] [stderr] Original diagnostics will follow.
[INFO] [stderr] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_pending.rs:91:17
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 111 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_pending.rs:91:17
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 158 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_pending.rs:91:17
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 203 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_pending.rs:91:17
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 256 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_pending.rs:91:17
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 309 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_pending.rs:91:17
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 343 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_pending.rs:91:17
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 375 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 7 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `cancel`
[INFO] [stderr] 
[INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files:
[INFO] [stderr] 
[INFO] [stderr]   * tests/cancel.rs
[INFO] [stderr] 
[INFO] [stderr] This likely indicates a bug in either rustc or cargo itself,
[INFO] [stderr] and we would appreciate a bug report! You're likely to see 
[INFO] [stderr] a number of compiler warnings after this message which cargo
[INFO] [stderr] attempted to fix but failed. If you could open an issue at
[INFO] [stderr] https://github.com/rust-lang/rust/issues
[INFO] [stderr] quoting the full output of this command we'd be very appreciative!
[INFO] [stderr] Note that you may be able to make some more progress in the near-term
[INFO] [stderr] fixing code with the `--broken-code` flag
[INFO] [stderr] 
[INFO] [stderr] The following errors were reported:
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/cancel.rs:95:25
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 116 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/cancel.rs:95:25
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 139 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: `let` expressions are not supported here
[INFO] [stderr]    --> tests/cancel.rs:95:25
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 179 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: only supported directly in conditions of `if`- and `while`-expressions
[INFO] [stderr]     = note: as well as when nested within `&&` and parenthesis in those conditions
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/cancel.rs:95:33
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 116 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/cancel.rs:95:25
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 116 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/cancel.rs:95:33
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 139 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/cancel.rs:95:25
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 139 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/cancel.rs:95:33
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                                 ^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 179 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error[E0658]: `let` expressions in this position are experimental
[INFO] [stderr]    --> tests/cancel.rs:95:25
[INFO] [stderr]     |
[INFO] [stderr] 95  |                 let _ = let _ = let _ = &guard;
[INFO] [stderr]     |                         ^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 179 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stderr]     |     ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: see issue #53667 <https://github.com/rust-lang/rust/issues/53667> for more information
[INFO] [stderr]     = help: add `#![feature(let_chains)]` to the crate attributes to enable
[INFO] [stderr]     = help: you can write `matches!(<expr>, <pattern>)` instead of `let <pattern> = <expr>`
[INFO] [stderr]     = note: this error originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] error: aborting due to 9 previous errors
[INFO] [stderr] 
[INFO] [stderr] For more information about this error, try `rustc --explain E0658`.
[INFO] [stderr] Original diagnostics will follow.
[INFO] [stderr] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]   --> tests/basic.rs:78:17
[INFO] [stdout]    |
[INFO] [stdout] 78 |                 &guard;
[INFO] [stdout]    |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 97 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]    |     ---------------------------------------- in this macro invocation
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]    = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]    |
[INFO] [stdout] 78 |                 let _ = &guard;
[INFO] [stdout]    |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/basic.rs:78:17
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 124 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/basic.rs:78:17
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 145 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/basic.rs:78:17
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 166 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/basic.rs:78:17
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 187 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/basic.rs:78:17
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 208 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/basic.rs:78:17
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 229 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 78  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 7 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/cancel.rs:95:17
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 116 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/cancel.rs:95:17
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 139 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/cancel.rs:95:17
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 179 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 3 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 6.52s
[INFO] [stderr] Running `cargo check` to verify 2021
[INFO] [stderr]     Checking async-task-ffi v4.1.1 (/tmp/fixit)
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/cancel.rs:95:17
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 116 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/cancel.rs:95:17
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 139 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/cancel.rs:95:17
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 179 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 3 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/ready.rs:95:17
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 114 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/ready.rs:95:17
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 160 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/ready.rs:95:17
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 195 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/ready.rs:95:17
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 226 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 95  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 4 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0509]: cannot move out of type `DropGuard`, which implements the `Drop` trait
[INFO] [stdout]    --> tests/basic.rs:331:57
[INFO] [stdout]     |
[INFO] [stdout] 331 |     let (runnable, _) = async_task_ffi::spawn(async {}, move |runnable| {
[INFO] [stdout]     |                                                         ^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                                         |
[INFO] [stdout]     |                                                         cannot move out of here
[INFO] [stdout]     |                                                         move out of `guard.0` occurs here
[INFO] [stdout] 332 |         assert_eq!(guard.0.load(Ordering::SeqCst), 0);
[INFO] [stdout]     |                    -------
[INFO] [stdout]     |                    |
[INFO] [stdout]     |                    move occurs because `guard.0` has type `AtomicUsize`, which does not implement the `Copy` trait
[INFO] [stdout]     |                    move occurs due to use in closure
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: aborting due to previous error
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0509`.
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_ready.rs:97:17
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 117 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_ready.rs:97:17
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 159 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_ready.rs:97:17
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 202 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_ready.rs:97:17
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 245 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/panic.rs:83:17
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 102 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_ready.rs:97:17
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 280 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 97  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/panic.rs:83:17
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 130 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/panic.rs:83:17
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 151 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/panic.rs:83:17
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 179 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `async-task-ffi` due to 2 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/panic.rs:83:17
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 211 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/panic.rs:83:17
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 241 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 83  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 5 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 6 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_pending.rs:91:17
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 111 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_pending.rs:91:17
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 158 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_pending.rs:91:17
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 203 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_pending.rs:91:17
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 256 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_pending.rs:91:17
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 309 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_pending.rs:91:17
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 343 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_pending.rs:91:17
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 375 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 91  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 7 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_panic.rs:100:17
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 124 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_panic.rs:100:17
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 170 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_panic.rs:100:17
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 215 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_panic.rs:100:17
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 268 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/waker_panic.rs:100:17
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 321 |     schedule!(s, d, chan, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 100 |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 117 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_must_use)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 138 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 159 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 180 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 5 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 214 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 247 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 280 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 322 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused borrow that must be used
[INFO] [stdout]    --> tests/join.rs:96:17
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 &guard;
[INFO] [stdout]     |                 ^^^^^^ the borrow produces a value
[INFO] [stdout] ...
[INFO] [stdout] 359 |     schedule!(s, d, SCHEDULE, DATA, DROP_S);
[INFO] [stdout]     |     ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `schedule` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] help: use `let _ = ...` to ignore the resulting value
[INFO] [stdout]     |
[INFO] [stdout] 96  |                 let _ = &guard;
[INFO] [stdout]     |                 +++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 9 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: build failed
[INFO] [stderr] error: failed to check after updating to 2021
[INFO] [stderr] 
[INFO] [stderr] Caused by:
[INFO] [stderr]   process didn't exit successfully: `cargo check --frozen --all --all-targets --message-format=json` (exit status: 101)
[INFO] running `Command { std: "docker" "inspect" "6f307c4e7774a250ca637b42c83b615662f5f1c162ade611b7cd764de1d5d54b", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "6f307c4e7774a250ca637b42c83b615662f5f1c162ade611b7cd764de1d5d54b", kill_on_drop: false }`
[INFO] [stdout] 6f307c4e7774a250ca637b42c83b615662f5f1c162ade611b7cd764de1d5d54b