[INFO] cloning repository https://github.com/TheUnlocked/aoc-2023 [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/TheUnlocked/aoc-2023" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FTheUnlocked%2Faoc-2023", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FTheUnlocked%2Faoc-2023'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 4e23934463033d031a41fb8d4f6a5f750011721e [INFO] checking TheUnlocked/aoc-2023/4e23934463033d031a41fb8d4f6a5f750011721e against try#ccf408f4326a858c00dd845a64a86b16f360a801 for pr-129466-2 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FTheUnlocked%2Faoc-2023" "/workspace/builds/worker-7-tc2/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-7-tc2/source'... [INFO] [stderr] done. [INFO] validating manifest of git repo https://github.com/TheUnlocked/aoc-2023 on toolchain ccf408f4326a858c00dd845a64a86b16f360a801 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+ccf408f4326a858c00dd845a64a86b16f360a801" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking git repo https://github.com/TheUnlocked/aoc-2023 [INFO] finished tweaking git repo https://github.com/TheUnlocked/aoc-2023 [INFO] tweaked toml for git repo https://github.com/TheUnlocked/aoc-2023 written to /workspace/builds/worker-7-tc2/source/Cargo.toml [INFO] crate git repo https://github.com/TheUnlocked/aoc-2023 already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+ccf408f4326a858c00dd845a64a86b16f360a801" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:6252d7ea7fb8caaf7af6d800c5fb250a9cd862b9a7f9508afb3c54fa7fe1102e" "/opt/rustwide/cargo-home/bin/cargo" "+ccf408f4326a858c00dd845a64a86b16f360a801" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 2ad34a52f723ca505161517694878296430fe664cbdefd061e0aeb4a9e8af43d [INFO] running `Command { std: "docker" "start" "-a" "2ad34a52f723ca505161517694878296430fe664cbdefd061e0aeb4a9e8af43d", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "2ad34a52f723ca505161517694878296430fe664cbdefd061e0aeb4a9e8af43d", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "2ad34a52f723ca505161517694878296430fe664cbdefd061e0aeb4a9e8af43d", kill_on_drop: false }` [INFO] [stdout] 2ad34a52f723ca505161517694878296430fe664cbdefd061e0aeb4a9e8af43d [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:6252d7ea7fb8caaf7af6d800c5fb250a9cd862b9a7f9508afb3c54fa7fe1102e" "/opt/rustwide/cargo-home/bin/cargo" "+ccf408f4326a858c00dd845a64a86b16f360a801" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] d5c925d8d7ddc937f1b63f8ac55ba513b25348c88c0f3bbf92d830ba258431b9 [INFO] running `Command { std: "docker" "start" "-a" "d5c925d8d7ddc937f1b63f8ac55ba513b25348c88c0f3bbf92d830ba258431b9", kill_on_drop: false }` [INFO] [stderr] Copying to /tmp/fixit [INFO] [stderr] Running `cargo fix --edition` [INFO] [stderr] Migrating Cargo.toml from 2021 edition to 2024 [INFO] [stderr] Compiling proc-macro2 v1.0.70 [INFO] [stderr] Compiling siphasher v0.3.11 [INFO] [stderr] Compiling rand_core v0.6.4 [INFO] [stderr] Checking memchr v2.6.4 [INFO] [stderr] Checking regex-syntax v0.8.2 [INFO] [stderr] Checking either v1.9.0 [INFO] [stderr] Checking fluid-let v1.0.0 [INFO] [stderr] Compiling indoc v2.0.4 [INFO] [stderr] Checking colored v2.1.0 [INFO] [stderr] Compiling rand v0.8.5 [INFO] [stderr] Checking phf_shared v0.11.2 [INFO] [stderr] Checking itertools v0.12.0 [INFO] [stderr] Checking aho-corasick v1.1.2 [INFO] [stderr] Compiling phf_generator v0.11.2 [INFO] [stderr] Compiling quote v1.0.33 [INFO] [stderr] Compiling syn v2.0.39 [INFO] [stderr] Checking regex-automata v0.4.3 [INFO] [stderr] Compiling phf_macros v0.11.2 [INFO] [stderr] Checking regex v1.10.2 [INFO] [stderr] Checking phf v0.11.2 [INFO] [stderr] Checking aoc-2023 v0.1.0 (/tmp/fixit) [INFO] [stderr] Migrating src/lib.rs from 2021 edition to 2024 [INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `aoc_2023` [INFO] [stderr] [INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files: [INFO] [stderr] [INFO] [stderr] * src/lib.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[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/lib.rs:20:13 [INFO] [stderr] | [INFO] [stderr] 20 | use $inputPath:expr_2021; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/lib.rs:50:6 [INFO] [stderr] | [INFO] [stderr] 50 | ($body:expr_2021; $($tail:tt)*) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/lib.rs:65:6 [INFO] [stderr] | [INFO] [stderr] 65 | ($input:expr_2021,) => {}; [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/lib.rs:66:6 [INFO] [stderr] | [INFO] [stderr] 66 | ($input:expr_2021, $_:expr_2021; $($tail:tt)*) => { $crate::run_parts!($input, $($tail)*) }; [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:20:24 [INFO] [stdout] | [INFO] [stdout] 20 | use $inputPath:expr; [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] = note: `--force-warn edition-2024-expr-fragment-specifier` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 20 | use $inputPath:expr_2021; [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:50:12 [INFO] [stdout] | [INFO] [stdout] 50 | ($body:expr; $($tail:tt)*) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 50 | ($body:expr_2021; $($tail:tt)*) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] | [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:65:13 [INFO] [stdout] | [INFO] [stdout] 65 | ($input:expr,) => {}; [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 65 | ($input:expr_2021,) => {}; [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:66:13 [INFO] [stdout] | [INFO] [stdout] 66 | ($input:expr, $_:expr; $($tail:tt)*) => { $crate::run_parts!($input, $($tail)*) }; [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 66 | ($input:expr_2021, $_:expr; $($tail:tt)*) => { $crate::run_parts!($input, $($tail)*) }; [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:66:22 [INFO] [stdout] | [INFO] [stdout] 66 | ($input:expr, $_:expr; $($tail:tt)*) => { $crate::run_parts!($input, $($tail)*) }; [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 66 | ($input:expr, $_:expr_2021; $($tail:tt)*) => { $crate::run_parts!($input, $($tail)*) }; [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:68:16 [INFO] [stdout] | [INFO] [stdout] 68 | $input:expr, [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 68 | $input:expr_2021, [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:89:13 [INFO] [stdout] | [INFO] [stdout] 89 | ($fluid:expr, $then:block) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 89 | ($fluid:expr_2021, $then:block) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:98:44 [INFO] [stdout] | [INFO] [stdout] 98 | ($part:ident( $input:tt ) == $expected:expr) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 98 | ($part:ident( $input:tt ) == $expected:expr_2021) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] --> src/lib.rs:66:24 [INFO] [stdout] warning: 8 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] | [INFO] [stderr] 66 | ($input:expr_2021, $_:expr_2021; $($tail:tt)*) => { $crate::run_parts!($input, $($tail)*) }; [INFO] [stderr] | ^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/lib.rs:68:9 [INFO] [stderr] | [INFO] [stderr] 68 | $input:expr_2021, [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/lib.rs:89:6 [INFO] [stderr] | [INFO] [stderr] 89 | ($fluid:expr_2021, $then:block) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/lib.rs:98:34 [INFO] [stderr] | [INFO] [stderr] 98 | ($part:ident( $input:tt ) == $expected:expr_2021) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error: aborting due to 8 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 `aoc_2023` [INFO] [stderr] [INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files: [INFO] [stderr] [INFO] [stderr] * src/lib.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[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/lib.rs:20:13 [INFO] [stderr] | [INFO] [stderr] 20 | use $inputPath:expr_2021; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/lib.rs:50:6 [INFO] [stderr] | [INFO] [stderr] 50 | ($body:expr_2021; $($tail:tt)*) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/lib.rs:65:6 [INFO] [stderr] | [INFO] [stderr] 65 | ($input:expr_2021,) => {}; [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/lib.rs:66:6 [INFO] [stderr] | [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:20:24 [INFO] [stdout] | [INFO] [stdout] 20 | use $inputPath:expr; [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] = note: `--force-warn edition-2024-expr-fragment-specifier` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 20 | use $inputPath:expr_2021; [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] 66 | ($input:expr_2021, $_:expr_2021; $($tail:tt)*) => { $crate::run_parts!($input, $($tail)*) }; [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:50:12 [INFO] [stdout] | [INFO] [stdout] 50 | ($body:expr; $($tail:tt)*) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 50 | ($body:expr_2021; $($tail:tt)*) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:65:13 [INFO] [stdout] | [INFO] [stdout] 65 | ($input:expr,) => {}; [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 65 | ($input:expr_2021,) => {}; [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] | [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:66:13 [INFO] [stdout] | [INFO] [stdout] 66 | ($input:expr, $_:expr; $($tail:tt)*) => { $crate::run_parts!($input, $($tail)*) }; [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 66 | ($input:expr_2021, $_:expr; $($tail:tt)*) => { $crate::run_parts!($input, $($tail)*) }; [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:66:22 [INFO] [stdout] | [INFO] [stdout] 66 | ($input:expr, $_:expr; $($tail:tt)*) => { $crate::run_parts!($input, $($tail)*) }; [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 66 | ($input:expr, $_:expr_2021; $($tail:tt)*) => { $crate::run_parts!($input, $($tail)*) }; [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:68:16 [INFO] [stdout] | [INFO] [stdout] 68 | $input:expr, [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 68 | $input:expr_2021, [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:89:13 [INFO] [stdout] | [INFO] [stdout] 89 | ($fluid:expr, $then:block) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 89 | ($fluid:expr_2021, $then:block) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/lib.rs:98:44 [INFO] [stdout] | [INFO] [stdout] 98 | ($part:ident( $input:tt ) == $expected:expr) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 98 | ($part:ident( $input:tt ) == $expected:expr_2021) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stdout] warning: 8 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] --> src/lib.rs:66:24 [INFO] [stderr] | [INFO] [stderr] 66 | ($input:expr_2021, $_:expr_2021; $($tail:tt)*) => { $crate::run_parts!($input, $($tail)*) }; [INFO] [stderr] | ^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/lib.rs:68:9 [INFO] [stderr] | [INFO] [stderr] 68 | $input:expr_2021, [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/lib.rs:89:6 [INFO] [stderr] | [INFO] [stderr] 89 | ($fluid:expr_2021, $then:block) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/lib.rs:98:34 [INFO] [stderr] | [INFO] [stderr] 98 | ($part:ident( $input:tt ) == $expected:expr_2021) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error: aborting due to 8 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] Migrating src/bin/day6.rs from 2021 edition to 2024 [INFO] [stderr] Fixed /tmp/fixit/src/lib.rs (1 fix) [INFO] [stderr] Migrating src/bin/day9.rs from 2021 edition to 2024 [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day6.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day6.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 71 | | [INFO] [stdout] 72 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day6.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day6.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 71 | | [INFO] [stdout] 72 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day6.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day6.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 71 | | [INFO] [stdout] 72 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day6.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day6.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 71 | | [INFO] [stdout] 72 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Migrating src/bin/day10.rs from 2021 edition to 2024 [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day9.rs:5:1 [INFO] [stdout] | [INFO] [stdout] 5 | / aoc! { [INFO] [stdout] 6 | | use "./inputs/day9.txt"; [INFO] [stdout] 7 | | [INFO] [stdout] 8 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 51 | | [INFO] [stdout] 52 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day9.rs:5:1 [INFO] [stdout] | [INFO] [stdout] 5 | / aoc! { [INFO] [stdout] 6 | | use "./inputs/day9.txt"; [INFO] [stdout] 7 | | [INFO] [stdout] 8 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 51 | | [INFO] [stdout] 52 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day9.rs:5:1 [INFO] [stdout] | [INFO] [stdout] 5 | / aoc! { [INFO] [stdout] 6 | | use "./inputs/day9.txt"; [INFO] [stdout] 7 | | [INFO] [stdout] 8 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 51 | | [INFO] [stdout] 52 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day9.rs:5:1 [INFO] [stdout] | [INFO] [stdout] 5 | / aoc! { [INFO] [stdout] 6 | | use "./inputs/day9.txt"; [INFO] [stdout] 7 | | [INFO] [stdout] 8 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 51 | | [INFO] [stdout] 52 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Migrating src/bin/day13.rs from 2021 edition to 2024 [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day10.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day10.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 315 | | [INFO] [stdout] 316 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day10.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day10.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 315 | | [INFO] [stdout] 316 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day10.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day10.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 315 | | [INFO] [stdout] 316 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day10.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day10.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 315 | | [INFO] [stdout] 316 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Migrating src/bin/day12.rs from 2021 edition to 2024 [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day13.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day13.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 149 | | [INFO] [stdout] 150 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day13.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day13.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 149 | | [INFO] [stdout] 150 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day13.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day13.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 149 | | [INFO] [stdout] 150 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day13.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day13.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 149 | | [INFO] [stdout] 150 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `day12` [INFO] [stderr] [INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files: [INFO] [stderr] [INFO] [stderr] * src/bin/day12.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[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/bin/day12.rs:147:22 [INFO] [stderr] | [INFO] [stderr] 147 | ($progress:expr_2021, $n:expr_2021) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/bin/day12.rs:147:43 [INFO] [stderr] | [INFO] [stderr] 147 | ($progress:expr_2021, $n:expr_2021) => { [INFO] [stderr] | ^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error: aborting due to 2 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] Migrating src/bin/day14.rs from 2021 edition to 2024 [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/bin/day12.rs:147:32 [INFO] [stdout] | [INFO] [stdout] 147 | ($progress:expr, $n:expr) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] = note: `--force-warn edition-2024-expr-fragment-specifier` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 147 | ($progress:expr_2021, $n:expr) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/bin/day12.rs:147:41 [INFO] [stdout] | [INFO] [stdout] 147 | ($progress:expr, $n:expr) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 147 | ($progress:expr, $n:expr_2021) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day12.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day12.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 233 | | [INFO] [stdout] 234 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day12.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day12.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 233 | | [INFO] [stdout] 234 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day12.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day12.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 233 | | [INFO] [stdout] 234 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day12.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day12.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 233 | | [INFO] [stdout] 234 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 4 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day14.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day14.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 139 | | [INFO] [stdout] 140 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day14.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day14.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 139 | | [INFO] [stdout] 140 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day14.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day14.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 139 | | [INFO] [stdout] 140 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day14.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day14.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 139 | | [INFO] [stdout] 140 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Migrating src/bin/day2.rs from 2021 edition to 2024 [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day13.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day13.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 149 | | [INFO] [stdout] 150 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day13.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day13.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 149 | | [INFO] [stdout] 150 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day13.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day13.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 149 | | [INFO] [stdout] 150 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day13.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day13.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 149 | | [INFO] [stdout] 150 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Migrating src/bin/day5.rs from 2021 edition to 2024 [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day2.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day2.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 78 | | [INFO] [stdout] 79 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day2.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day2.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 78 | | [INFO] [stdout] 79 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day2.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day2.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 78 | | [INFO] [stdout] 79 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day2.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day2.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 78 | | [INFO] [stdout] 79 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day5.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day5.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 236 | | [INFO] [stdout] 237 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day5.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day5.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 236 | | [INFO] [stdout] 237 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day5.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day5.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 236 | | [INFO] [stdout] 237 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day5.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day5.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 236 | | [INFO] [stdout] 237 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Migrating src/bin/day7.rs from 2021 edition to 2024 [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day14.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day14.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 139 | | [INFO] [stdout] 140 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day14.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day14.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 139 | | [INFO] [stdout] 140 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day14.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day14.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 139 | | [INFO] [stdout] 140 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day14.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day14.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 139 | | [INFO] [stdout] 140 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day7.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day7.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 204 | | [INFO] [stdout] 205 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day7.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day7.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 204 | | [INFO] [stdout] 205 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day7.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day7.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 204 | | [INFO] [stdout] 205 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day7.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day7.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 204 | | [INFO] [stdout] 205 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Migrating src/bin/day11.rs from 2021 edition to 2024 [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day7.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day7.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 204 | | [INFO] [stdout] 205 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day7.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day7.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 204 | | [INFO] [stdout] 205 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day7.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day7.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 204 | | [INFO] [stdout] 205 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day7.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day7.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 204 | | [INFO] [stdout] 205 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Migrating src/bin/day1.rs from 2021 edition to 2024 [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day11.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day11.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 110 | | [INFO] [stdout] 111 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day11.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day11.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 110 | | [INFO] [stdout] 111 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day11.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day11.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 110 | | [INFO] [stdout] 111 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day11.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day11.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 110 | | [INFO] [stdout] 111 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Migrating src/bin/day3.rs from 2021 edition to 2024 [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day1.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day1.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!( [INFO] [stdout] ... | [INFO] [stdout] 76 | | [INFO] [stdout] 77 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day1.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day1.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!( [INFO] [stdout] ... | [INFO] [stdout] 76 | | [INFO] [stdout] 77 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day1.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day1.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!( [INFO] [stdout] ... | [INFO] [stdout] 76 | | [INFO] [stdout] 77 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day1.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day1.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!( [INFO] [stdout] ... | [INFO] [stdout] 76 | | [INFO] [stdout] 77 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `day3` [INFO] [stderr] [INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files: [INFO] [stderr] [INFO] [stderr] * src/bin/day3.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] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/bin/day3.rs:52:21 [INFO] [stdout] | [INFO] [stdout] 52 | ($x:expr, $then:block) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] = note: `--force-warn edition-2024-expr-fragment-specifier` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 52 | ($x:expr_2021, $then:block) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Note that you may be able to make some more progress in the near-term [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/bin/day3.rs:123:21 [INFO] [stdout] | [INFO] [stdout] 123 | ($x:expr, $then:block) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 123 | ($x:expr_2021, $then:block) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] fixing code with the `--broken-code` flag [INFO] [stderr] [INFO] [stderr] The following errors were reported: [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/bin/day3.rs:52:18 [INFO] [stderr] | [INFO] [stderr] 52 | ($x:expr_2021, $then:block) => { [INFO] [stderr] | ^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/bin/day3.rs:123:18 [INFO] [stderr] | [INFO] [stderr] 123 | ($x:expr_2021, $then:block) => { [INFO] [stderr] | ^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error: aborting due to 2 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: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day3.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day3.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 160 | | [INFO] [stdout] 161 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day3.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day3.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 160 | | [INFO] [stdout] 161 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day3.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day3.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 160 | | [INFO] [stdout] 161 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day3.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day3.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 160 | | [INFO] [stdout] 161 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 4 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Migrating src/bin/day8.rs from 2021 edition to 2024 [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day6.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day6.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 71 | | [INFO] [stdout] 72 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day6.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day6.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 71 | | [INFO] [stdout] 72 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day6.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day6.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 71 | | [INFO] [stdout] 72 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day6.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day6.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 71 | | [INFO] [stdout] 72 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Fixed src/bin/day8.rs (1 fix) [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day8.rs:8:1 [INFO] [stdout] | [INFO] [stdout] 8 | / aoc! { [INFO] [stdout] 9 | | use "./inputs/day8.txt"; [INFO] [stdout] 10 | | [INFO] [stdout] 11 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 245 | | [INFO] [stdout] 246 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day8.rs:8:1 [INFO] [stdout] | [INFO] [stdout] 8 | / aoc! { [INFO] [stdout] 9 | | use "./inputs/day8.txt"; [INFO] [stdout] 10 | | [INFO] [stdout] 11 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 245 | | [INFO] [stdout] 246 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day8.rs:8:1 [INFO] [stdout] | [INFO] [stdout] 8 | / aoc! { [INFO] [stdout] 9 | | use "./inputs/day8.txt"; [INFO] [stdout] 10 | | [INFO] [stdout] 11 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 245 | | [INFO] [stdout] 246 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day8.rs:8:1 [INFO] [stdout] | [INFO] [stdout] 8 | / aoc! { [INFO] [stdout] 9 | | use "./inputs/day8.txt"; [INFO] [stdout] 10 | | [INFO] [stdout] 11 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 245 | | [INFO] [stdout] 246 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day9.rs:5:1 [INFO] [stdout] | [INFO] [stdout] 5 | / aoc! { [INFO] [stdout] 6 | | use "./inputs/day9.txt"; [INFO] [stdout] 7 | | [INFO] [stdout] 8 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 51 | | [INFO] [stdout] 52 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day9.rs:5:1 [INFO] [stdout] | [INFO] [stdout] 5 | / aoc! { [INFO] [stdout] 6 | | use "./inputs/day9.txt"; [INFO] [stdout] 7 | | [INFO] [stdout] 8 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 51 | | [INFO] [stdout] 52 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day9.rs:5:1 [INFO] [stdout] | [INFO] [stdout] 5 | / aoc! { [INFO] [stdout] 6 | | use "./inputs/day9.txt"; [INFO] [stdout] 7 | | [INFO] [stdout] 8 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 51 | | [INFO] [stdout] 52 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day9.rs:5:1 [INFO] [stdout] | [INFO] [stdout] 5 | / aoc! { [INFO] [stdout] 6 | | use "./inputs/day9.txt"; [INFO] [stdout] 7 | | [INFO] [stdout] 8 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 51 | | [INFO] [stdout] 52 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `day12` [INFO] [stderr] [INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files: [INFO] [stderr] [INFO] [stderr] * src/bin/day12.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[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/bin/day12.rs:147:22 [INFO] [stderr] | [INFO] [stderr] 147 | ($progress:expr_2021, $n:expr_2021) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/bin/day12.rs:147:43 [INFO] [stderr] | [INFO] [stderr] 147 | ($progress:expr_2021, $n:expr_2021) => { [INFO] [stderr] | ^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error: aborting due to 2 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: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/bin/day12.rs:147:32 [INFO] [stdout] | [INFO] [stdout] 147 | ($progress:expr, $n:expr) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] = note: `--force-warn edition-2024-expr-fragment-specifier` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 147 | ($progress:expr_2021, $n:expr) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/bin/day12.rs:147:41 [INFO] [stdout] | [INFO] [stdout] 147 | ($progress:expr, $n:expr) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 147 | ($progress:expr, $n:expr_2021) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day12.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day12.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 233 | | [INFO] [stdout] 234 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day12.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day12.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 233 | | [INFO] [stdout] 234 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day12.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day12.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 233 | | [INFO] [stdout] 234 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day12.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day12.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 233 | | [INFO] [stdout] 234 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 4 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day2.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day2.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 78 | | [INFO] [stdout] 79 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day2.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day2.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 78 | | [INFO] [stdout] 79 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day2.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day2.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 78 | | [INFO] [stdout] 79 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day2.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day2.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 78 | | [INFO] [stdout] 79 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day1.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day1.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!( [INFO] [stdout] ... | [INFO] [stdout] 76 | | [INFO] [stdout] 77 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day1.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day1.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!( [INFO] [stdout] ... | [INFO] [stdout] 76 | | [INFO] [stdout] 77 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day1.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day1.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!( [INFO] [stdout] ... | [INFO] [stdout] 76 | | [INFO] [stdout] 77 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day1.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day1.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!( [INFO] [stdout] ... | [INFO] [stdout] 76 | | [INFO] [stdout] 77 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day8.rs:8:1 [INFO] [stdout] | [INFO] [stdout] 8 | / aoc! { [INFO] [stdout] 9 | | use "./inputs/day8.txt"; [INFO] [stdout] 10 | | [INFO] [stdout] 11 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 245 | | [INFO] [stdout] 246 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day8.rs:8:1 [INFO] [stdout] | [INFO] [stdout] 8 | / aoc! { [INFO] [stdout] 9 | | use "./inputs/day8.txt"; [INFO] [stdout] 10 | | [INFO] [stdout] 11 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 245 | | [INFO] [stdout] 246 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day8.rs:8:1 [INFO] [stdout] | [INFO] [stdout] 8 | / aoc! { [INFO] [stdout] 9 | | use "./inputs/day8.txt"; [INFO] [stdout] 10 | | [INFO] [stdout] 11 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 245 | | [INFO] [stdout] 246 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day8.rs:8:1 [INFO] [stdout] | [INFO] [stdout] 8 | / aoc! { [INFO] [stdout] 9 | | use "./inputs/day8.txt"; [INFO] [stdout] 10 | | [INFO] [stdout] 11 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 245 | | [INFO] [stdout] 246 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Migrating src/bin/day4.rs from 2021 edition to 2024 [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day11.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day11.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 110 | | [INFO] [stdout] 111 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day11.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day11.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 110 | | [INFO] [stdout] 111 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day11.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day11.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 110 | | [INFO] [stdout] 111 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day11.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day11.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 110 | | [INFO] [stdout] 111 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day4.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day4.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 96 | | [INFO] [stdout] 97 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day4.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day4.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 96 | | [INFO] [stdout] 97 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day4.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day4.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 96 | | [INFO] [stdout] 97 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day4.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day4.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 96 | | [INFO] [stdout] 97 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day10.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day10.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 315 | | [INFO] [stdout] 316 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day10.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day10.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 315 | | [INFO] [stdout] 316 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day10.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day10.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 315 | | [INFO] [stdout] 316 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day10.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day10.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 315 | | [INFO] [stdout] 316 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `day3` [INFO] [stderr] [INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files: [INFO] [stderr] [INFO] [stderr] * src/bin/day3.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[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/bin/day3.rs:52:18 [INFO] [stderr] | [INFO] [stderr] 52 | ($x:expr_2021, $then:block) => { [INFO] [stderr] | ^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/bin/day3.rs:123:18 [INFO] [stderr] | [INFO] [stderr] 123 | ($x:expr_2021, $then:block) => { [INFO] [stderr] | ^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error: aborting due to 2 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: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/bin/day3.rs:52:21 [INFO] [stdout] | [INFO] [stdout] 52 | ($x:expr, $then:block) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] = note: `--force-warn edition-2024-expr-fragment-specifier` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 52 | ($x:expr_2021, $then:block) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/bin/day3.rs:123:21 [INFO] [stdout] | [INFO] [stdout] 123 | ($x:expr, $then:block) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 123 | ($x:expr_2021, $then:block) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day3.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day3.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 160 | | [INFO] [stdout] 161 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day3.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day3.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 160 | | [INFO] [stdout] 161 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day3.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day3.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 160 | | [INFO] [stdout] 161 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day3.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day3.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 160 | | [INFO] [stdout] 161 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 4 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day4.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day4.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 96 | | [INFO] [stdout] 97 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day4.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day4.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 96 | | [INFO] [stdout] 97 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day4.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day4.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 96 | | [INFO] [stdout] 97 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day4.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day4.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 96 | | [INFO] [stdout] 97 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day5.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day5.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 236 | | [INFO] [stdout] 237 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day5.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day5.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 236 | | [INFO] [stdout] 237 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl AocResult` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/bin/day5.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day5.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 236 | | [INFO] [stdout] 237 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/bin/day5.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day5.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 236 | | [INFO] [stdout] 237 | | } [INFO] [stdout] | |_^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: this warning originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 2 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 5.11s [INFO] [stderr] Running `cargo check` to verify 2024 [INFO] [stderr] Checking aoc-2023 v0.1.0 (/tmp/fixit) [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day6.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day6.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 71 | | [INFO] [stdout] 72 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day2.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day2.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 78 | | [INFO] [stdout] 79 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day14.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day14.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 139 | | [INFO] [stdout] 140 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day6.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day6.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 71 | | [INFO] [stdout] 72 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day2.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day2.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 78 | | [INFO] [stdout] 79 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day2.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day2.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 78 | | [INFO] [stdout] 79 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day8.rs:8:1 [INFO] [stdout] | [INFO] [stdout] 8 | / aoc! { [INFO] [stdout] 9 | | use "./inputs/day8.txt"; [INFO] [stdout] 10 | | [INFO] [stdout] 11 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 245 | | [INFO] [stdout] 246 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day2.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day2.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 78 | | [INFO] [stdout] 79 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day1.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day1.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!( [INFO] [stdout] ... | [INFO] [stdout] 76 | | [INFO] [stdout] 77 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day12.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day12.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 233 | | [INFO] [stdout] 234 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day1.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day1.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!( [INFO] [stdout] ... | [INFO] [stdout] 76 | | [INFO] [stdout] 77 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day1.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day1.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!( [INFO] [stdout] ... | [INFO] [stdout] 76 | | [INFO] [stdout] 77 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day14.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day14.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 139 | | [INFO] [stdout] 140 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day3.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day3.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 160 | | [INFO] [stdout] 161 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day8.rs:8:1 [INFO] [stdout] | [INFO] [stdout] 8 | / aoc! { [INFO] [stdout] 9 | | use "./inputs/day8.txt"; [INFO] [stdout] 10 | | [INFO] [stdout] 11 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 245 | | [INFO] [stdout] 246 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day14.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day14.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 139 | | [INFO] [stdout] 140 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day13.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day13.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 149 | | [INFO] [stdout] 150 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day1.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / aoc! { [INFO] [stdout] 5 | | use "./inputs/day1.txt"; [INFO] [stdout] 6 | | [INFO] [stdout] 7 | | example!( [INFO] [stdout] ... | [INFO] [stdout] 76 | | [INFO] [stdout] 77 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day14.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day14.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 139 | | [INFO] [stdout] 140 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day13.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day13.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 149 | | [INFO] [stdout] 150 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day12.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day12.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 233 | | [INFO] [stdout] 234 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day3.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | / aoc! { [INFO] [stdout] 4 | | use "./inputs/day3.txt"; [INFO] [stdout] 5 | | [INFO] [stdout] 6 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 160 | | [INFO] [stdout] 161 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day10.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day10.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 315 | | [INFO] [stdout] 316 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day4.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day4.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 96 | | [INFO] [stdout] 97 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day4.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day4.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 96 | | [INFO] [stdout] 97 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day7.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day7.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 204 | | [INFO] [stdout] 205 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day10.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day10.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 315 | | [INFO] [stdout] 316 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day12.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day12.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 233 | | [INFO] [stdout] 234 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day7.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day7.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 204 | | [INFO] [stdout] 205 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day12.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | / aoc! { [INFO] [stdout] 7 | | use "./inputs/day12.txt"; [INFO] [stdout] 8 | | [INFO] [stdout] 9 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 233 | | [INFO] [stdout] 234 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day7.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day7.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 204 | | [INFO] [stdout] 205 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0178]: expected a path on the left-hand side of `+`, not `impl AocResult` [INFO] [stdout] --> src/bin/day7.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | / aoc! { [INFO] [stdout] 8 | | use "./inputs/day7.txt"; [INFO] [stdout] 9 | | [INFO] [stdout] 10 | | example!(part1( [INFO] [stdout] ... | [INFO] [stdout] 204 | | [INFO] [stdout] 205 | | } [INFO] [stdout] | |_^ expected a path [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `$crate::run_top_level_stmts` which comes from the expansion of the macro `aoc` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `aoc-2023` (bin "day6") due to 3 previous errors [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stderr] error: could not compile `aoc-2023` (bin "day1" test) due to 3 previous errors [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stderr] error: could not compile `aoc-2023` (bin "day2") due to 3 previous errors [INFO] [stderr] error: could not compile `aoc-2023` (bin "day13" test) due to 3 previous errors [INFO] [stderr] error: could not compile `aoc-2023` (bin "day1") due to 3 previous errors [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stderr] error: could not compile `aoc-2023` (bin "day2" test) due to 3 previous errors [INFO] [stderr] error: could not compile `aoc-2023` (bin "day4" test) due to 3 previous errors [INFO] [stderr] error: could not compile `aoc-2023` (bin "day14") due to 3 previous errors [INFO] [stderr] error: could not compile `aoc-2023` (bin "day14" test) due to 3 previous errors [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stderr] error: could not compile `aoc-2023` (bin "day3") due to 3 previous errors [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stderr] error: could not compile `aoc-2023` (bin "day7") due to 3 previous errors [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stderr] error: could not compile `aoc-2023` (bin "day8") due to 3 previous errors [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stderr] error: could not compile `aoc-2023` (bin "day7" test) due to 3 previous errors [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0178`. [INFO] [stdout] [INFO] [stderr] error: could not compile `aoc-2023` (bin "day12") due to 3 previous errors [INFO] [stderr] error: could not compile `aoc-2023` (bin "day10") due to 3 previous errors [INFO] [stderr] error: could not compile `aoc-2023` (bin "day12" test) due to 3 previous errors [INFO] [stderr] error: failed to check after updating to 2024 [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" "d5c925d8d7ddc937f1b63f8ac55ba513b25348c88c0f3bbf92d830ba258431b9", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "d5c925d8d7ddc937f1b63f8ac55ba513b25348c88c0f3bbf92d830ba258431b9", kill_on_drop: false }` [INFO] [stdout] d5c925d8d7ddc937f1b63f8ac55ba513b25348c88c0f3bbf92d830ba258431b9