[INFO] fetching crate async-task 4.0.3... [INFO] checking async-task-4.0.3 against try#a7a572ce3edd6d476191fbfe92c9c1986e009b34 for pr-87190-3 [INFO] extracting crate async-task 4.0.3 into /workspace/builds/worker-78/source [INFO] validating manifest of crates.io crate async-task 4.0.3 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 4.0.3 [INFO] finished tweaking crates.io crate async-task 4.0.3 [INFO] tweaked toml for crates.io crate async-task 4.0.3 written to /workspace/builds/worker-78/source/Cargo.toml [INFO] crate crates.io crate async-task 4.0.3 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] Downloading crates ... [INFO] [stderr] Downloaded fastrand v1.3.5 [INFO] [stderr] Downloaded async-executor v1.1.1 [INFO] [stderr] Downloaded async-channel v1.4.2 [INFO] [stderr] Downloaded event-listener v2.4.0 [INFO] [stderr] Downloaded nb-connect v1.0.0 [INFO] [stderr] Downloaded async-fs v1.3.0 [INFO] [stderr] Downloaded blocking v1.0.0 [INFO] [stderr] Downloaded async-process v1.0.0 [INFO] [stderr] Downloaded async-mutex v1.3.0 [INFO] [stderr] Downloaded async-semaphore v1.1.0 [INFO] [stderr] Downloaded async-lock v2.1.3 [INFO] [stderr] Downloaded async-barrier v1.0.1 [INFO] [stderr] Downloaded async-rwlock v1.1.0 [INFO] [stderr] Downloaded async-io v1.1.2 [INFO] [stderr] Downloaded polling v1.0.3 [INFO] [stderr] Downloaded async-net v1.3.0 [INFO] [stderr] Downloaded futures-lite v1.7.0 [INFO] [stderr] Downloaded smol v1.0.1 [INFO] [stderr] Downloaded flume v0.9.0 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-78/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-78/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] 1b6b43453fe59760fec9ddd0fbddc31038d43f26e2de7a667c15fe8cffc6c1c4 [INFO] running `Command { std: "docker" "start" "-a" "1b6b43453fe59760fec9ddd0fbddc31038d43f26e2de7a667c15fe8cffc6c1c4", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "1b6b43453fe59760fec9ddd0fbddc31038d43f26e2de7a667c15fe8cffc6c1c4", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "1b6b43453fe59760fec9ddd0fbddc31038d43f26e2de7a667c15fe8cffc6c1c4", kill_on_drop: false }` [INFO] [stdout] 1b6b43453fe59760fec9ddd0fbddc31038d43f26e2de7a667c15fe8cffc6c1c4 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-78/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-78/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] 248d9d6cd8f02ba94c73daaae48eb0906536ea594e26b7166c5149fed4fdfb88 [INFO] running `Command { std: "docker" "start" "-a" "248d9d6cd8f02ba94c73daaae48eb0906536ea594e26b7166c5149fed4fdfb88", kill_on_drop: false }` [INFO] [stderr] Copying to /tmp/fixit [INFO] [stderr] Running `cargo fix --edition` [INFO] [stderr] Checking event-listener v2.4.0 [INFO] [stderr] Compiling memchr v2.3.3 [INFO] [stderr] Compiling libc v0.2.77 [INFO] [stderr] Checking futures-io v0.3.5 [INFO] [stderr] Checking fastrand v1.3.5 [INFO] [stderr] Checking once_cell v1.4.1 [INFO] [stderr] Compiling log v0.4.11 [INFO] [stderr] Checking vec-arena v1.0.0 [INFO] [stderr] Checking async-task v3.0.0 [INFO] [stderr] Checking easy-parallel v3.1.0 [INFO] [stderr] Checking async-task v4.0.3 (/tmp/fixit) [INFO] [stderr] Checking concurrent-queue v1.2.2 [INFO] [stderr] Checking lock_api v0.4.1 [INFO] [stderr] Migrating src/lib.rs from 2018 edition to 2021 [INFO] [stderr] Checking async-mutex v1.3.0 [INFO] [stderr] Checking async-semaphore v1.1.0 [INFO] [stderr] Checking spinning_top v0.2.2 [INFO] [stderr] Checking async-channel v1.4.2 [INFO] [stderr] Checking async-barrier v1.0.1 [INFO] [stderr] Checking async-rwlock v1.1.0 [INFO] [stderr] Checking flume v0.9.0 [INFO] [stderr] Checking async-lock v2.1.3 [INFO] [stderr] Checking futures-lite v1.7.0 [INFO] [stderr] Checking polling v1.0.3 [INFO] [stderr] Checking nb-connect v1.0.0 [INFO] [stderr] Checking signal-hook-registry v1.2.1 [INFO] [stderr] Checking signal-hook v0.1.16 [INFO] [stderr] Checking blocking v1.0.0 [INFO] [stderr] Checking async-io v1.1.2 [INFO] [stderr] Checking async-executor v1.1.1 [INFO] [stderr] Checking async-fs v1.3.0 [INFO] [stderr] Checking async-net v1.3.0 [INFO] [stderr] Checking async-process v1.0.0 [INFO] [stderr] Checking smol v1.0.1 [INFO] [stderr] Migrating benches/spawn.rs from 2018 edition to 2021 [INFO] [stderr] Migrating tests/ready.rs from 2018 edition to 2021 [INFO] [stderr] Migrating tests/basic.rs from 2018 edition to 2021 [INFO] [stderr] Migrating tests/waker_pending.rs from 2018 edition to 2021 [INFO] [stderr] Migrating examples/spawn-local.rs from 2018 edition to 2021 [INFO] [stderr] Migrating examples/spawn-on-thread.rs from 2018 edition to 2021 [INFO] [stderr] Migrating examples/spawn.rs from 2018 edition to 2021 [INFO] [stderr] Migrating tests/cancel.rs from 2018 edition to 2021 [INFO] [stderr] Migrating tests/waker_ready.rs from 2018 edition to 2021 [INFO] [stderr] Migrating tests/join.rs from 2018 edition to 2021 [INFO] [stderr] Migrating tests/panic.rs from 2018 edition to 2021 [INFO] [stderr] Migrating tests/waker_panic.rs from 2018 edition to 2021 [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:84:25 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 98 | schedule!(s, SCHEDULE, 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:84:25 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 140 | schedule!(s, SCHEDULE, 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:84:25 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 173 | schedule!(s, SCHEDULE, 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:84:25 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 202 | schedule!(s, SCHEDULE, 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:84:41 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 98 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:33 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 98 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:25 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 98 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:41 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 140 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:33 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 140 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:25 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 140 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:41 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 173 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:33 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 173 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:25 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 173 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:41 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 202 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:33 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 202 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:25 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 202 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/ready.rs:84:17 [INFO] [stdout] | [INFO] [stdout] 84 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 98 | schedule!(s, SCHEDULE, 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] 84 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/ready.rs:84:17 [INFO] [stdout] | [INFO] [stdout] 84 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 140 | schedule!(s, SCHEDULE, 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] 84 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/ready.rs:84:17 [INFO] [stdout] | [INFO] [stdout] 84 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 173 | schedule!(s, SCHEDULE, 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] 84 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/ready.rs:84:17 [INFO] [stdout] | [INFO] [stdout] 84 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 202 | schedule!(s, SCHEDULE, 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] 84 | 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 `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:67:25 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 81 | schedule!(s, SCHEDULE, 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:67:25 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 105 | schedule!(s, SCHEDULE, 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:67:25 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 124 | schedule!(s, SCHEDULE, 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:67:25 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 143 | schedule!(s, SCHEDULE, 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:67:25 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 162 | schedule!(s, SCHEDULE, 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:67:25 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 181 | schedule!(s, SCHEDULE, 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:67:25 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 200 | schedule!(s, SCHEDULE, 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:67:65 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 81 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:57 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 81 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:49 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 81 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:41 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 81 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:33 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 81 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:25 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 81 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:65 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 105 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:57 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 105 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:49 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 105 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:41 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 105 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:33 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 105 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:25 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 105 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:65 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 124 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:57 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 124 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:49 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 124 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:41 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 124 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:33 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 124 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:25 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 124 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:65 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 143 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:57 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 143 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:49 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 143 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:41 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 143 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:33 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 143 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:25 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 143 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:65 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 162 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:57 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 162 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:49 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 162 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:41 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 162 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:33 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 162 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:25 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 162 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:65 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 181 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:57 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 181 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:49 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 181 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:41 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 181 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:33 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 181 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:25 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 181 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:65 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 200 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:57 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 200 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:49 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 200 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:41 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 200 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:33 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 200 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:67:25 [INFO] [stderr] | [INFO] [stderr] 67 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 200 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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/basic.rs:67:17 [INFO] [stdout] | [INFO] [stdout] 67 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 81 | schedule!(s, SCHEDULE, 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] 67 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/basic.rs:67:17 [INFO] [stdout] | [INFO] [stdout] 67 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 105 | schedule!(s, SCHEDULE, 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] 67 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/basic.rs:67:17 [INFO] [stdout] | [INFO] [stdout] 67 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 124 | schedule!(s, SCHEDULE, 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] 67 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/basic.rs:67:17 [INFO] [stdout] | [INFO] [stdout] 67 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 143 | schedule!(s, SCHEDULE, 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] 67 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/basic.rs:67:17 [INFO] [stdout] | [INFO] [stdout] 67 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 162 | schedule!(s, SCHEDULE, 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] 67 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/basic.rs:67:17 [INFO] [stdout] | [INFO] [stdout] 67 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 181 | schedule!(s, SCHEDULE, 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] 67 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/basic.rs:67:17 [INFO] [stdout] | [INFO] [stdout] 67 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 200 | schedule!(s, SCHEDULE, 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] 67 | 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 `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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 100 | schedule!(s, SCHEDULE, 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 119 | schedule!(s, SCHEDULE, 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 138 | schedule!(s, SCHEDULE, 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 157 | schedule!(s, SCHEDULE, 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 217 | schedule!(s, SCHEDULE, 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 248 | schedule!(s, SCHEDULE, 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 286 | schedule!(s, SCHEDULE, 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 320 | schedule!(s, SCHEDULE, 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:85:81 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 100 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:73 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 100 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:65 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 100 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:57 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 100 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:49 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 100 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:41 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 100 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:33 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 100 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 100 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:81 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 119 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:73 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 119 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:65 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 119 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:57 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 119 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:49 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 119 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:41 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 119 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:33 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 119 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 119 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:81 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 138 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:73 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 138 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:65 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 138 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:57 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 138 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:49 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 138 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:41 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 138 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:33 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 138 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 138 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:81 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 157 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:73 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 157 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:65 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 157 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:57 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 157 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:49 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 157 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:41 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 157 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:33 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 157 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 157 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:81 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:73 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:65 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:57 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:49 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:41 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:33 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:81 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 217 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:73 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 217 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:65 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 217 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:57 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 217 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:49 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 217 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:41 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 217 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:33 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 217 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 217 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:81 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 248 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:73 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 248 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:65 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 248 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:57 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 248 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:49 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 248 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:41 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 248 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:33 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 248 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 248 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:81 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 286 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:73 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 286 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:65 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 286 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:57 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 286 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:49 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 286 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:41 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 286 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:33 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 286 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 286 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:81 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 320 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:73 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 320 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:65 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 320 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:57 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 320 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:49 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 320 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:41 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 320 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:33 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 320 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:85:25 [INFO] [stderr] | [INFO] [stderr] 85 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 320 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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] [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:86:25 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 103 | schedule!(s, chan, SCHEDULE, 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:86:25 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 142 | schedule!(s, chan, SCHEDULE, 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:86:25 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 181 | schedule!(s, chan, SCHEDULE, 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:86:25 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 220 | schedule!(s, chan, SCHEDULE, 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:86:25 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 252 | schedule!(s, chan, SCHEDULE, 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:86:49 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 103 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:41 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 103 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:33 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 103 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:25 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 103 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:49 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 142 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:41 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 142 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:33 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 142 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:25 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 142 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:49 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 181 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:41 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 181 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:33 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 181 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:25 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 181 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:49 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 220 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:41 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 220 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:33 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 220 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:25 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 220 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:49 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 252 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:41 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 252 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:33 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 252 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:86:25 [INFO] [stderr] | [INFO] [stderr] 86 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 252 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 100 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 119 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 138 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 157 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 186 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 217 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 248 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 286 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 320 | schedule!(s, SCHEDULE, 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] 85 | 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/waker_ready.rs:86:17 [INFO] [stdout] | [INFO] [stdout] 86 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 103 | schedule!(s, chan, SCHEDULE, 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] 86 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_ready.rs:86:17 [INFO] [stdout] | [INFO] [stdout] 86 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 142 | schedule!(s, chan, SCHEDULE, 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] 86 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_ready.rs:86:17 [INFO] [stdout] | [INFO] [stdout] 86 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 181 | schedule!(s, chan, SCHEDULE, 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] 86 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_ready.rs:86:17 [INFO] [stdout] | [INFO] [stdout] 86 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 220 | schedule!(s, chan, SCHEDULE, 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] 86 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_ready.rs:86:17 [INFO] [stdout] | [INFO] [stdout] 86 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 252 | schedule!(s, chan, SCHEDULE, 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] 86 | 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 `waker_pending` [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:80:25 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 97 | schedule!(s, chan, SCHEDULE, 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:80:25 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 141 | schedule!(s, chan, SCHEDULE, 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:80:25 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 183 | schedule!(s, chan, SCHEDULE, 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:80:25 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 232 | schedule!(s, chan, SCHEDULE, 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:80:25 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 281 | schedule!(s, chan, SCHEDULE, 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:80:25 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 312 | schedule!(s, chan, SCHEDULE, 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:80:25 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 341 | schedule!(s, chan, SCHEDULE, 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:80:65 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 97 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:57 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 97 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:49 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 97 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:41 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 97 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:33 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 97 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:25 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 97 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:65 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 141 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:57 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 141 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:49 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 141 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:41 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 141 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:33 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 141 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:25 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 141 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:65 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 183 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:57 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 183 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:49 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 183 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:41 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 183 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:33 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 183 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:25 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 183 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:65 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 232 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:57 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 232 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:49 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 232 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:41 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 232 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:33 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 232 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:25 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 232 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:65 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 281 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:57 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 281 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:49 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 281 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:41 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 281 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:33 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 281 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:25 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 281 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:65 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 312 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:57 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 312 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:49 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 312 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:41 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 312 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:33 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 312 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:25 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 312 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:65 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 341 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:57 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 341 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:49 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 341 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:41 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 341 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:33 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 341 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:25 [INFO] [stderr] | [INFO] [stderr] 80 | let _ = let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 341 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:80:17 [INFO] [stdout] | [INFO] [stdout] 80 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 97 | schedule!(s, chan, SCHEDULE, 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] 80 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_pending.rs:80:17 [INFO] [stdout] | [INFO] [stdout] 80 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 141 | schedule!(s, chan, SCHEDULE, 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] 80 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_pending.rs:80:17 [INFO] [stdout] | [INFO] [stdout] 80 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 183 | schedule!(s, chan, SCHEDULE, 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] 80 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_pending.rs:80:17 [INFO] [stdout] | [INFO] [stdout] 80 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 232 | schedule!(s, chan, SCHEDULE, 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] 80 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_pending.rs:80:17 [INFO] [stdout] | [INFO] [stdout] 80 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 281 | schedule!(s, chan, SCHEDULE, 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] 80 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_pending.rs:80:17 [INFO] [stdout] | [INFO] [stdout] 80 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 312 | schedule!(s, chan, SCHEDULE, 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] 80 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_pending.rs:80:17 [INFO] [stdout] | [INFO] [stdout] 80 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 341 | schedule!(s, chan, SCHEDULE, 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] 80 | 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:84:25 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 99 | schedule!(s, SCHEDULE, 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:84:25 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 120 | schedule!(s, SCHEDULE, 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:84:25 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 157 | schedule!(s, SCHEDULE, 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:84:33 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 99 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:25 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 99 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:33 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 120 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:25 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 120 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:33 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 157 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:84:25 [INFO] [stderr] | [INFO] [stderr] 84 | let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 157 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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/cancel.rs:84:17 [INFO] [stdout] | [INFO] [stdout] 84 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 99 | schedule!(s, SCHEDULE, 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] 84 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/cancel.rs:84:17 [INFO] [stdout] | [INFO] [stdout] 84 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 120 | schedule!(s, SCHEDULE, 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] 84 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/cancel.rs:84:17 [INFO] [stdout] | [INFO] [stdout] 84 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 157 | schedule!(s, SCHEDULE, 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] 84 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 3 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:72:25 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 86 | schedule!(s, SCHEDULE, 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:72:25 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 112 | schedule!(s, SCHEDULE, 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:72:25 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 131 | schedule!(s, SCHEDULE, 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:72:25 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 156 | schedule!(s, SCHEDULE, 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:72:25 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, 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:72:25 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 213 | schedule!(s, SCHEDULE, 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:72:57 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 86 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:49 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 86 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:41 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 86 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:33 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 86 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:25 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 86 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:57 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 112 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:49 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 112 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:41 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 112 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:33 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 112 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:25 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 112 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:57 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 131 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:49 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 131 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:41 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 131 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:33 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 131 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:25 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 131 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:57 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 156 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:49 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 156 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:41 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 156 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:33 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 156 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:25 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 156 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:57 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:49 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:41 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:33 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:25 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 186 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:57 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 213 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:49 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 213 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:41 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 213 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:33 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 213 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:72:25 [INFO] [stderr] | [INFO] [stderr] 72 | let _ = let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 213 | schedule!(s, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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/panic.rs:72:17 [INFO] [stdout] | [INFO] [stdout] 72 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 86 | schedule!(s, SCHEDULE, 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] 72 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/panic.rs:72:17 [INFO] [stdout] | [INFO] [stdout] 72 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 112 | schedule!(s, SCHEDULE, 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] 72 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/panic.rs:72:17 [INFO] [stdout] | [INFO] [stdout] 72 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 131 | schedule!(s, SCHEDULE, 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] 72 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/panic.rs:72:17 [INFO] [stdout] | [INFO] [stdout] 72 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 156 | schedule!(s, SCHEDULE, 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] 72 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/panic.rs:72:17 [INFO] [stdout] | [INFO] [stdout] 72 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 186 | schedule!(s, SCHEDULE, 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] 72 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/panic.rs:72:17 [INFO] [stdout] | [INFO] [stdout] 72 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 213 | schedule!(s, SCHEDULE, 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] 72 | 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:89:25 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 110 | schedule!(s, chan, SCHEDULE, 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:89:25 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 153 | schedule!(s, chan, SCHEDULE, 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:89:25 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 195 | schedule!(s, chan, SCHEDULE, 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:89:25 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 244 | schedule!(s, chan, SCHEDULE, 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:89:25 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 293 | schedule!(s, chan, SCHEDULE, 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:89:49 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 110 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:41 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 110 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:33 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 110 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:25 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 110 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:49 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 153 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:41 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 153 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:33 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 153 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:25 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 153 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:49 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 195 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:41 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 195 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:33 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 195 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:25 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 195 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:49 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 244 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:41 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 244 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:33 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 244 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:25 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 244 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:49 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 293 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:41 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 293 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:33 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 293 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:25 [INFO] [stderr] | [INFO] [stderr] 89 | let _ = let _ = let _ = let _ = let _ = &guard; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] ... [INFO] [stderr] 293 | schedule!(s, chan, SCHEDULE, DROP_S); [INFO] [stderr] | ------------------------------------- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = note: see issue #53667 for more information [INFO] [stderr] = help: add `#![feature(let_chains)]` to the crate attributes to enable [INFO] [stderr] = help: you can write `matches!(, )` instead of `let = ` [INFO] [stderr] = 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:89:17 [INFO] [stdout] | [INFO] [stdout] 89 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 110 | schedule!(s, chan, SCHEDULE, 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] 89 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_panic.rs:89:17 [INFO] [stdout] | [INFO] [stdout] 89 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 153 | schedule!(s, chan, SCHEDULE, 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] 89 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_panic.rs:89:17 [INFO] [stdout] | [INFO] [stdout] 89 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 195 | schedule!(s, chan, SCHEDULE, 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] 89 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_panic.rs:89:17 [INFO] [stdout] | [INFO] [stdout] 89 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 244 | schedule!(s, chan, SCHEDULE, 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] 89 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_panic.rs:89:17 [INFO] [stdout] | [INFO] [stdout] 89 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 293 | schedule!(s, chan, SCHEDULE, 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] 89 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 5 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 6.10s [INFO] [stderr] Running `cargo check` to verify 2021 [INFO] [stderr] Checking async-task v4.0.3 (/tmp/fixit) [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/ready.rs:84:17 [INFO] [stdout] | [INFO] [stdout] 84 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 98 | schedule!(s, SCHEDULE, 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] 84 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/ready.rs:84:17 [INFO] [stdout] | [INFO] [stdout] 84 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 140 | schedule!(s, SCHEDULE, 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] 84 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/ready.rs:84:17 [INFO] [stdout] | [INFO] [stdout] 84 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 173 | schedule!(s, SCHEDULE, 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] 84 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/ready.rs:84:17 [INFO] [stdout] | [INFO] [stdout] 84 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 202 | schedule!(s, SCHEDULE, 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] 84 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 4 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/panic.rs:72:17 [INFO] [stdout] | [INFO] [stdout] 72 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 86 | schedule!(s, SCHEDULE, 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] 72 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/panic.rs:72:17 [INFO] [stdout] | [INFO] [stdout] 72 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 112 | schedule!(s, SCHEDULE, 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] 72 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/panic.rs:72:17 [INFO] [stdout] | [INFO] [stdout] 72 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 131 | schedule!(s, SCHEDULE, 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] 72 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/panic.rs:72:17 [INFO] [stdout] | [INFO] [stdout] 72 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 156 | schedule!(s, SCHEDULE, 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] 72 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/panic.rs:72:17 [INFO] [stdout] | [INFO] [stdout] 72 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 186 | schedule!(s, SCHEDULE, 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] 72 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/panic.rs:72:17 [INFO] [stdout] | [INFO] [stdout] 72 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 213 | schedule!(s, SCHEDULE, 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] 72 | let _ = &guard; [INFO] [stdout] | +++++++ [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/cancel.rs:84:17 [INFO] [stdout] | [INFO] [stdout] 84 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 99 | schedule!(s, SCHEDULE, 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] 84 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/cancel.rs:84:17 [INFO] [stdout] | [INFO] [stdout] 84 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 120 | schedule!(s, SCHEDULE, 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] 84 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/cancel.rs:84:17 [INFO] [stdout] | [INFO] [stdout] 84 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 157 | schedule!(s, SCHEDULE, 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] 84 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 3 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:276:53 [INFO] [stdout] | [INFO] [stdout] 276 | let (runnable, _) = async_task::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] 277 | 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] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_ready.rs:86:17 [INFO] [stdout] | [INFO] [stdout] 86 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 103 | schedule!(s, chan, SCHEDULE, 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] 86 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_ready.rs:86:17 [INFO] [stdout] | [INFO] [stdout] 86 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 142 | schedule!(s, chan, SCHEDULE, 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] 86 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_ready.rs:86:17 [INFO] [stdout] | [INFO] [stdout] 86 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 181 | schedule!(s, chan, SCHEDULE, 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] 86 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_ready.rs:86:17 [INFO] [stdout] | [INFO] [stdout] 86 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 220 | schedule!(s, chan, SCHEDULE, 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] 86 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_ready.rs:86:17 [INFO] [stdout] | [INFO] [stdout] 86 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 252 | schedule!(s, chan, SCHEDULE, 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] 86 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_panic.rs:89:17 [INFO] [stdout] | [INFO] [stdout] 89 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 110 | schedule!(s, chan, SCHEDULE, 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] 89 | let _ = &guard; [INFO] [stdout] | +++++++ [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_panic.rs:89:17 [INFO] [stdout] | [INFO] [stdout] 89 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 153 | schedule!(s, chan, SCHEDULE, 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] 89 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_panic.rs:89:17 [INFO] [stdout] | [INFO] [stdout] 89 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 195 | schedule!(s, chan, SCHEDULE, 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] 89 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_panic.rs:89:17 [INFO] [stdout] | [INFO] [stdout] 89 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 244 | schedule!(s, chan, SCHEDULE, 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] 89 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_panic.rs:89:17 [INFO] [stdout] | [INFO] [stdout] 89 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 293 | schedule!(s, chan, SCHEDULE, 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] 89 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 5 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 5 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `async-task` 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/waker_pending.rs:80:17 [INFO] [stdout] | [INFO] [stdout] 80 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 97 | schedule!(s, chan, SCHEDULE, 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] 80 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_pending.rs:80:17 [INFO] [stdout] | [INFO] [stdout] 80 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 141 | schedule!(s, chan, SCHEDULE, 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] 80 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_pending.rs:80:17 [INFO] [stdout] | [INFO] [stdout] 80 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 183 | schedule!(s, chan, SCHEDULE, 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] 80 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_pending.rs:80:17 [INFO] [stdout] | [INFO] [stdout] 80 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 232 | schedule!(s, chan, SCHEDULE, 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] 80 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_pending.rs:80:17 [INFO] [stdout] | [INFO] [stdout] 80 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 281 | schedule!(s, chan, SCHEDULE, 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] 80 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_pending.rs:80:17 [INFO] [stdout] | [INFO] [stdout] 80 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 312 | schedule!(s, chan, SCHEDULE, 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] 80 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/waker_pending.rs:80:17 [INFO] [stdout] | [INFO] [stdout] 80 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 341 | schedule!(s, chan, SCHEDULE, 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] 80 | 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/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 100 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 119 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 138 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 157 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 186 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 217 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 248 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 286 | schedule!(s, SCHEDULE, 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] 85 | let _ = &guard; [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused borrow that must be used [INFO] [stdout] --> tests/join.rs:85:17 [INFO] [stdout] | [INFO] [stdout] 85 | &guard; [INFO] [stdout] | ^^^^^^ the borrow produces a value [INFO] [stdout] ... [INFO] [stdout] 320 | schedule!(s, SCHEDULE, 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] 85 | 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" "248d9d6cd8f02ba94c73daaae48eb0906536ea594e26b7166c5149fed4fdfb88", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "248d9d6cd8f02ba94c73daaae48eb0906536ea594e26b7166c5149fed4fdfb88", kill_on_drop: false }` [INFO] [stdout] 248d9d6cd8f02ba94c73daaae48eb0906536ea594e26b7166c5149fed4fdfb88