[INFO] cloning repository https://github.com/Siddid-Soni/advent-of-code-2024 [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/Siddid-Soni/advent-of-code-2024" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FSiddid-Soni%2Fadvent-of-code-2024", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FSiddid-Soni%2Fadvent-of-code-2024'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 915fb2b13fc06d331299d1921f625c39b6f55a58 [INFO] linting Siddid-Soni/advent-of-code-2024 against nightly for clippy-nonminimal_bool-denied [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FSiddid-Soni%2Fadvent-of-code-2024" "/workspace/builds/worker-1-tc1/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-1-tc1/source'... [INFO] [stderr] done. [INFO] started tweaking git repo https://github.com/Siddid-Soni/advent-of-code-2024 [INFO] finished tweaking git repo https://github.com/Siddid-Soni/advent-of-code-2024 [INFO] tweaked toml for git repo https://github.com/Siddid-Soni/advent-of-code-2024 written to /workspace/builds/worker-1-tc1/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/Siddid-Soni/advent-of-code-2024 on toolchain nightly [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/Siddid-Soni/advent-of-code-2024 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" "+nightly" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded divan-macros v0.1.17 [INFO] [stderr] Downloaded condtype v1.3.0 [INFO] [stderr] Downloaded code-timing-macros v0.0.5 [INFO] [stderr] Downloaded cached_proc_macro v0.23.0 [INFO] [stderr] Downloaded terminal_size v0.4.1 [INFO] [stderr] Downloaded cached v0.54.0 [INFO] [stderr] Downloaded divan v0.1.17 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:d429b63d4308055ea97f60fb1d3dfca48854a00942f1bd2ad806beaf015945ec" "/opt/rustwide/cargo-home/bin/cargo" "+nightly" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] b18d36dcedf36fa9b6d5cbfd89abc9d855ec6636a313789e668de9263025b0a6 [INFO] running `Command { std: "docker" "start" "-a" "b18d36dcedf36fa9b6d5cbfd89abc9d855ec6636a313789e668de9263025b0a6", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "b18d36dcedf36fa9b6d5cbfd89abc9d855ec6636a313789e668de9263025b0a6", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "b18d36dcedf36fa9b6d5cbfd89abc9d855ec6636a313789e668de9263025b0a6", kill_on_drop: false }` [INFO] [stdout] b18d36dcedf36fa9b6d5cbfd89abc9d855ec6636a313789e668de9263025b0a6 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:d429b63d4308055ea97f60fb1d3dfca48854a00942f1bd2ad806beaf015945ec" "/opt/rustwide/cargo-home/bin/cargo" "+nightly" "clippy" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 99fe3a542191823e4fa232c4bbaccb275091172f2e54fa21164de9443fafb4d3 [INFO] running `Command { std: "docker" "start" "-a" "99fe3a542191823e4fa232c4bbaccb275091172f2e54fa21164de9443fafb4d3", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v1.0.92 [INFO] [stderr] Compiling rustix v0.38.41 [INFO] [stderr] Compiling libc v0.2.167 [INFO] [stderr] Checking condtype v1.3.0 [INFO] [stderr] Checking regex-lite v0.1.6 [INFO] [stderr] Checking regex-syntax v0.8.5 [INFO] [stderr] Compiling ahash v0.8.11 [INFO] [stderr] Checking cached_proc_macro_types v0.1.1 [INFO] [stderr] Checking web-time v1.1.0 [INFO] [stderr] Checking hashbrown v0.14.5 [INFO] [stderr] Compiling quote v1.0.37 [INFO] [stderr] Checking terminal_size v0.4.1 [INFO] [stderr] Compiling syn v2.0.90 [INFO] [stderr] Checking clap_builder v4.5.23 [INFO] [stderr] Checking regex-automata v0.4.9 [INFO] [stderr] Checking clap v4.5.23 [INFO] [stderr] Compiling darling_core v0.20.10 [INFO] [stderr] Checking regex v1.11.1 [INFO] [stderr] Compiling code-timing-macros v0.0.5 [INFO] [stderr] Compiling divan-macros v0.1.17 [INFO] [stderr] Compiling thiserror-impl v1.0.69 [INFO] [stderr] Checking day-15 v0.1.0 (/opt/rustwide/workdir/day-15) [INFO] [stderr] Checking day-02 v0.1.0 (/opt/rustwide/workdir/day-02) [INFO] [stderr] Checking day-17 v0.1.0 (/opt/rustwide/workdir/day-17) [INFO] [stderr] Checking day-07 v0.1.0 (/opt/rustwide/workdir/day-07) [INFO] [stderr] Checking day-13 v0.1.0 (/opt/rustwide/workdir/day-13) [INFO] [stderr] Checking day-22 v0.1.0 (/opt/rustwide/workdir/day-22) [INFO] [stderr] Checking day-04 v0.1.0 (/opt/rustwide/workdir/day-04) [INFO] [stderr] Checking day-19 v0.1.0 (/opt/rustwide/workdir/day-19) [INFO] [stderr] Checking day-20 v0.1.0 (/opt/rustwide/workdir/day-20) [INFO] [stderr] Checking day-10 v0.1.0 (/opt/rustwide/workdir/day-10) [INFO] [stderr] Checking day-21 v0.1.0 (/opt/rustwide/workdir/day-21) [INFO] [stderr] Checking day-05 v0.1.0 (/opt/rustwide/workdir/day-05) [INFO] [stderr] Checking day-16 v0.1.0 (/opt/rustwide/workdir/day-16) [INFO] [stderr] Checking day-23 v0.1.0 (/opt/rustwide/workdir/day-23) [INFO] [stdout] warning: the loop variable `j` is used to index `grid` [INFO] [stdout] --> day-20/src/part1.rs:8:18 [INFO] [stdout] | [INFO] [stdout] 8 | for j in 0..grid[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] = note: `#[warn(clippy::needless_range_loop)]` on by default [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 8 - for j in 0..grid[0].len() { [INFO] [stdout] 8 + for (j, ) in grid.iter().enumerate().take(grid[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: length comparison to zero [INFO] [stdout] --> day-17/src/part2.rs:5:12 [INFO] [stdout] | [INFO] [stdout] 5 | if program.len() == 0 { return Some(ans); } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ help: using `is_empty` is clearer and more explicit: `program.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#len_zero [INFO] [stdout] = note: `#[warn(clippy::len_zero)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is used to index `grid` [INFO] [stdout] --> day-20/src/part2.rs:8:18 [INFO] [stdout] | [INFO] [stdout] 8 | for j in 0..grid[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 8 - for j in 0..grid[0].len() { [INFO] [stdout] 8 + for (j, ) in grid.iter().enumerate().take(grid[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this boolean expression can be simplified [INFO] [stdout] --> day-10/src/part1.rs:8:12 [INFO] [stdout] | [INFO] [stdout] 8 | if !(0<=r && r day-10/src/part1.rs:14:29 [INFO] [stdout] | [INFO] [stdout] 14 | dfs(r+1, c, next+1, &grid, visited) + dfs(r-1, c, next+1, &grid, visited) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] = note: `#[warn(clippy::needless_borrow)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking day-18 v0.1.0 (/opt/rustwide/workdir/day-18) [INFO] [stdout] warning: this expression creates a reference which is immediately dereferenced by the compiler [INFO] [stdout] --> day-10/src/part1.rs:14:67 [INFO] [stdout] | [INFO] [stdout] 14 | dfs(r+1, c, next+1, &grid, visited) + dfs(r-1, c, next+1, &grid, visited) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this expression creates a reference which is immediately dereferenced by the compiler [INFO] [stdout] --> day-10/src/part1.rs:15:39 [INFO] [stdout] | [INFO] [stdout] 15 | + dfs(r, c+1, next+1, &grid, visited) + dfs(r, c-1, next+1, &grid, visited) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this expression creates a reference which is immediately dereferenced by the compiler [INFO] [stdout] --> day-10/src/part1.rs:15:77 [INFO] [stdout] | [INFO] [stdout] 15 | + dfs(r, c+1, next+1, &grid, visited) + dfs(r, c-1, next+1, &grid, visited) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this boolean expression can be simplified [INFO] [stdout] --> day-10/src/part2.rs:8:12 [INFO] [stdout] | [INFO] [stdout] 8 | if !(0<=r && r day-10/src/part2.rs:13:29 [INFO] [stdout] | [INFO] [stdout] 13 | dfs(r+1, c, next+1, &grid) + dfs(r-1, c, next+1, &grid) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this expression creates a reference which is immediately dereferenced by the compiler [INFO] [stdout] --> day-10/src/part2.rs:13:58 [INFO] [stdout] | [INFO] [stdout] 13 | dfs(r+1, c, next+1, &grid) + dfs(r-1, c, next+1, &grid) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this expression creates a reference which is immediately dereferenced by the compiler [INFO] [stdout] --> day-10/src/part2.rs:14:39 [INFO] [stdout] | [INFO] [stdout] 14 | + dfs(r, c+1, next+1, &grid) + dfs(r, c-1, next+1, &grid) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this expression creates a reference which is immediately dereferenced by the compiler [INFO] [stdout] --> day-10/src/part2.rs:14:68 [INFO] [stdout] | [INFO] [stdout] 14 | + dfs(r, c+1, next+1, &grid) + dfs(r, c-1, next+1, &grid) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking day-14 v0.1.0 (/opt/rustwide/workdir/day-14) [INFO] [stdout] warning: comparison to empty slice [INFO] [stdout] --> day-19/src/lib.rs:12:33 [INFO] [stdout] | [INFO] [stdout] 12 | let lines = lines.split(|x| x == "").collect::>(); [INFO] [stdout] | ^^^^^^^ help: using `is_empty` is clearer and more explicit: `x.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#comparison_to_empty [INFO] [stdout] = note: `#[warn(clippy::comparison_to_empty)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking day-06 v0.1.0 (/opt/rustwide/workdir/day-06) [INFO] [stdout] warning: usage of `contains_key` followed by `insert` on a `HashMap` [INFO] [stdout] --> day-22/src/part2.rs:29:13 [INFO] [stdout] | [INFO] [stdout] 29 | if !seq_to_total.contains_key(&seq) { seq_to_total.insert(seq, 0); } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `seq_to_total.entry(seq).or_insert(0);` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#map_entry [INFO] [stdout] = note: `#[warn(clippy::map_entry)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking day-08 v0.1.0 (/opt/rustwide/workdir/day-08) [INFO] [stderr] Checking day-03 v0.1.0 (/opt/rustwide/workdir/day-03) [INFO] [stdout] warning: comparison to empty slice [INFO] [stdout] --> day-13/src/part1.rs:10:35 [INFO] [stdout] | [INFO] [stdout] 10 | let lines = binding.split(|x| x=="").collect::>(); [INFO] [stdout] | ^^^^^ help: using `is_empty` is clearer and more explicit: `x.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#comparison_to_empty [INFO] [stdout] = note: `#[warn(clippy::comparison_to_empty)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unneeded `return` statement [INFO] [stdout] --> day-07/src/part1.rs:8:5 [INFO] [stdout] | [INFO] [stdout] 8 | return false; [INFO] [stdout] | ^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_return [INFO] [stdout] = note: `#[warn(clippy::needless_return)]` on by default [INFO] [stdout] help: remove `return` [INFO] [stdout] | [INFO] [stdout] 8 - return false; [INFO] [stdout] 8 + false [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: writing `&Vec` instead of `&[_]` involves a new object where a slice will do [INFO] [stdout] --> day-07/src/part1.rs:4:33 [INFO] [stdout] | [INFO] [stdout] 4 | fn can_obtain(target:u64, nums: &Vec) -> bool { [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#ptr_arg [INFO] [stdout] = note: `#[warn(clippy::ptr_arg)]` on by default [INFO] [stdout] help: change this to [INFO] [stdout] | [INFO] [stdout] 4 - fn can_obtain(target:u64, nums: &Vec) -> bool { [INFO] [stdout] 4 + fn can_obtain(target:u64, nums: &[u64]) -> bool { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manual implementation of `.is_multiple_of()` [INFO] [stdout] --> day-07/src/part1.rs:6:8 [INFO] [stdout] | [INFO] [stdout] 6 | if target % nums[nums.len()-1] == 0 && can_obtain(target / nums[nums.len()-1],&nums[..nums.len()-1].to_vec()) {return true} [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: replace with: `target.is_multiple_of(nums[nums.len()-1])` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_is_multiple_of [INFO] [stdout] = note: `#[warn(clippy::manual_is_multiple_of)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: comparison to empty slice [INFO] [stdout] --> day-15/src/part1.rs:9:33 [INFO] [stdout] | [INFO] [stdout] 9 | let lines = lines.split(|x| x=="").collect::>(); [INFO] [stdout] | ^^^^^ help: using `is_empty` is clearer and more explicit: `x.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#comparison_to_empty [INFO] [stdout] = note: `#[warn(clippy::comparison_to_empty)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unneeded `return` statement [INFO] [stdout] --> day-07/src/part2.rs:11:5 [INFO] [stdout] | [INFO] [stdout] 11 | return false; [INFO] [stdout] | ^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_return [INFO] [stdout] help: remove `return` [INFO] [stdout] | [INFO] [stdout] 11 - return false; [INFO] [stdout] 11 + false [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: writing `&Vec` instead of `&[_]` involves a new object where a slice will do [INFO] [stdout] --> day-07/src/part2.rs:4:33 [INFO] [stdout] | [INFO] [stdout] 4 | fn can_obtain(target:u64, nums: &Vec) -> bool { [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#ptr_arg [INFO] [stdout] help: change this to [INFO] [stdout] | [INFO] [stdout] 4 - fn can_obtain(target:u64, nums: &Vec) -> bool { [INFO] [stdout] 4 + fn can_obtain(target:u64, nums: &[u64]) -> bool { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manual implementation of `.is_multiple_of()` [INFO] [stdout] --> day-07/src/part2.rs:6:8 [INFO] [stdout] | [INFO] [stdout] 6 | if target % nums[nums.len()-1] == 0 && can_obtain(target / nums[nums.len()-1],&nums[..nums.len()-1].to_vec()) {return true} [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: replace with: `target.is_multiple_of(nums[nums.len()-1])` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_is_multiple_of [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is used to index `grid` [INFO] [stdout] --> day-15/src/part1.rs:15:18 [INFO] [stdout] | [INFO] [stdout] 15 | for j in 0..grid[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] = note: `#[warn(clippy::needless_range_loop)]` on by default [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 15 - for j in 0..grid[0].len() { [INFO] [stdout] 15 + for (j, ) in grid.iter().enumerate().take(grid[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: comparison to empty slice [INFO] [stdout] --> day-13/src/part2.rs:10:35 [INFO] [stdout] | [INFO] [stdout] 10 | let lines = binding.split(|x| x=="").collect::>(); [INFO] [stdout] | ^^^^^ help: using `is_empty` is clearer and more explicit: `x.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#comparison_to_empty [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is used to index `grid` [INFO] [stdout] --> day-15/src/part1.rs:53:18 [INFO] [stdout] | [INFO] [stdout] 53 | for j in 0..grid[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 53 - for j in 0..grid[0].len() { [INFO] [stdout] 53 + for (j, ) in grid.iter().enumerate().take(grid[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `i` is used to index `grid` [INFO] [stdout] --> day-06/src/part1.rs:14:22 [INFO] [stdout] | [INFO] [stdout] 14 | 'outer: for i in 0..rows { [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] = note: `#[warn(clippy::needless_range_loop)]` on by default [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 14 - 'outer: for i in 0..rows { [INFO] [stdout] 14 + 'outer: for (i, ) in grid.iter().enumerate().take(rows) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is used to index `grid` [INFO] [stdout] --> day-06/src/part1.rs:15:18 [INFO] [stdout] | [INFO] [stdout] 15 | for j in 0..cols { [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 15 - for j in 0..cols { [INFO] [stdout] 15 + for (j, ) in grid.iter().enumerate().take(cols) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `row` is used to index `grid` [INFO] [stdout] --> day-06/src/part2.rs:12:16 [INFO] [stdout] | [INFO] [stdout] 12 | for row in 0..H { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 12 - for row in 0..H { [INFO] [stdout] 12 + for (row, ) in grid.iter().enumerate().take(H) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `col` is used to index `grid` [INFO] [stdout] --> day-06/src/part2.rs:13:20 [INFO] [stdout] | [INFO] [stdout] 13 | for col in 0..W { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 13 - for col in 0..W { [INFO] [stdout] 13 + for (col, ) in grid.iter().enumerate().take(W) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: comparison to empty slice [INFO] [stdout] --> day-15/src/part2.rs:9:33 [INFO] [stdout] | [INFO] [stdout] 9 | let lines = lines.split(|x| x=="").collect::>(); [INFO] [stdout] | ^^^^^ help: using `is_empty` is clearer and more explicit: `x.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#comparison_to_empty [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is only used to index `grid` [INFO] [stdout] --> day-15/src/part2.rs:15:18 [INFO] [stdout] | [INFO] [stdout] 15 | for j in 0..grid[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator [INFO] [stdout] | [INFO] [stdout] 15 - for j in 0..grid[0].len() { [INFO] [stdout] 15 + for in grid.iter().take(grid[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is used to index `grid_new` [INFO] [stdout] --> day-15/src/part2.rs:36:18 [INFO] [stdout] | [INFO] [stdout] 36 | for j in 0..grid_new[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 36 - for j in 0..grid_new[0].len() { [INFO] [stdout] 36 + for (j, ) in grid_new.iter().enumerate().take(grid_new[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is used to index `grid_new` [INFO] [stdout] --> day-15/src/part2.rs:88:18 [INFO] [stdout] | [INFO] [stdout] 88 | for j in 0..grid_new[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 88 - for j in 0..grid_new[0].len() { [INFO] [stdout] 88 + for (j, ) in grid_new.iter().enumerate().take(grid_new[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking day-12 v0.1.0 (/opt/rustwide/workdir/day-12) [INFO] [stdout] warning: usage of a legacy numeric constant [INFO] [stdout] --> day-14/src/part2.rs:9:22 [INFO] [stdout] | [INFO] [stdout] 9 | let mut min_sf = std::i32::MAX; [INFO] [stdout] | ^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#legacy_numeric_constants [INFO] [stdout] = note: `#[warn(clippy::legacy_numeric_constants)]` on by default [INFO] [stdout] help: use the associated constant instead [INFO] [stdout] | [INFO] [stdout] 9 - let mut min_sf = std::i32::MAX; [INFO] [stdout] 9 + let mut min_sf = i32::MAX; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking day-09 v0.1.0 (/opt/rustwide/workdir/day-09) [INFO] [stderr] Checking day-01 v0.1.0 (/opt/rustwide/workdir/day-01) [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-14/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-14/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-07/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-07/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: comparison to empty slice [INFO] [stdout] --> day-05/src/part1.rs:16:39 [INFO] [stdout] | [INFO] [stdout] 16 | let idx = lst.iter().position(|x| x=="").unwrap(); [INFO] [stdout] | ^^^^^ help: using `is_empty` is clearer and more explicit: `x.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#comparison_to_empty [INFO] [stdout] = note: `#[warn(clippy::comparison_to_empty)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: comparison to empty slice [INFO] [stdout] --> day-05/src/part2.rs:15:39 [INFO] [stdout] | [INFO] [stdout] 15 | let idx = lst.iter().position(|x| x=="").unwrap(); [INFO] [stdout] | ^^^^^ help: using `is_empty` is clearer and more explicit: `x.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#comparison_to_empty [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-03/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-03/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `col` is used to index `grid` [INFO] [stdout] --> day-16/src/part1.rs:33:20 [INFO] [stdout] | [INFO] [stdout] 33 | for col in 0..grid[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] = note: `#[warn(clippy::needless_range_loop)]` on by default [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 33 - for col in 0..grid[0].len() { [INFO] [stdout] 33 + for (col, ) in grid.iter().enumerate().take(grid[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: writing `&Vec` instead of `&[_]` involves a new object where a slice will do [INFO] [stdout] --> day-21/src/part1.rs:4:25 [INFO] [stdout] | [INFO] [stdout] 4 | fn get_sequence(keypad: &Vec>) -> HashMap::<(char,char), Vec> { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#ptr_arg [INFO] [stdout] = note: `#[warn(clippy::ptr_arg)]` on by default [INFO] [stdout] help: change this to [INFO] [stdout] | [INFO] [stdout] 4 - fn get_sequence(keypad: &Vec>) -> HashMap::<(char,char), Vec> { [INFO] [stdout] 4 + fn get_sequence(keypad: &[Vec]) -> HashMap::<(char,char), Vec> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `col` is used to index `grid` [INFO] [stdout] --> day-16/src/part2.rs:33:20 [INFO] [stdout] | [INFO] [stdout] 33 | for col in 0..grid[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 33 - for col in 0..grid[0].len() { [INFO] [stdout] 33 + for (col, ) in grid.iter().enumerate().take(grid[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `c` is used to index `keypad` [INFO] [stdout] --> day-21/src/part1.rs:7:18 [INFO] [stdout] | [INFO] [stdout] 7 | for c in 0..keypad[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] = note: `#[warn(clippy::needless_range_loop)]` on by default [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 7 - for c in 0..keypad[0].len() { [INFO] [stdout] 7 + for (c, ) in keypad.iter().enumerate().take(keypad[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: very complex type used. Consider factoring parts into `type` definitions [INFO] [stdout] --> day-16/src/part2.rs:45:24 [INFO] [stdout] | [INFO] [stdout] 45 | let mut backtrack: HashMap<(usize, usize, usize), HashSet<(usize, usize, usize)>> = HashMap::new(); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#type_complexity [INFO] [stdout] = note: `#[warn(clippy::type_complexity)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: writing `&Vec` instead of `&[_]` involves a new object where a slice will do [INFO] [stdout] --> day-21/src/part2.rs:5:25 [INFO] [stdout] | [INFO] [stdout] 5 | fn get_sequence(keypad: &Vec>) -> HashMap::<(char,char), Vec> { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#ptr_arg [INFO] [stdout] help: change this to [INFO] [stdout] | [INFO] [stdout] 5 - fn get_sequence(keypad: &Vec>) -> HashMap::<(char,char), Vec> { [INFO] [stdout] 5 + fn get_sequence(keypad: &[Vec]) -> HashMap::<(char,char), Vec> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of `or_insert` to construct default value [INFO] [stdout] --> day-16/src/part2.rs:64:89 [INFO] [stdout] | [INFO] [stdout] 64 | backtrack.entry((next_state.pos.0, next_state.pos.1, next_state.direc)).or_insert(HashSet::new()).clear(); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `or_default()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unwrap_or_default [INFO] [stdout] = note: `#[warn(clippy::unwrap_or_default)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `c` is used to index `keypad` [INFO] [stdout] --> day-21/src/part2.rs:8:18 [INFO] [stdout] | [INFO] [stdout] 8 | for c in 0..keypad[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 8 - for c in 0..keypad[0].len() { [INFO] [stdout] 8 + for (c, ) in keypad.iter().enumerate().take(keypad[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of `or_insert` to construct default value [INFO] [stdout] --> day-16/src/part2.rs:67:85 [INFO] [stdout] | [INFO] [stdout] 67 | ... backtrack.entry((next_state.pos.0, next_state.pos.1, next_state.direc)).or_insert(HashSet::new()).insert((pos.0, pos.1, direc)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `or_default()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unwrap_or_default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: found `.or(Some(…)).unwrap()` [INFO] [stdout] --> day-16/src/part2.rs:76:43 [INFO] [stdout] | [INFO] [stdout] 76 | for &prev in backtrack.get(&keys).or(Some(&HashSet::new())).unwrap() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `unwrap_or(&HashSet::new())` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#or_then_unwrap [INFO] [stdout] = note: `#[warn(clippy::or_then_unwrap)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unneeded `return` statement [INFO] [stdout] --> day-21/src/part2.rs:59:5 [INFO] [stdout] | [INFO] [stdout] 59 | return length; [INFO] [stdout] | ^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_return [INFO] [stdout] = note: `#[warn(clippy::needless_return)]` on by default [INFO] [stdout] help: remove `return` [INFO] [stdout] | [INFO] [stdout] 59 - return length; [INFO] [stdout] 59 + length [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: casting to the same type is unnecessary (`usize` -> `usize`) [INFO] [stdout] --> day-12/src/part1.rs:31:24 [INFO] [stdout] | [INFO] [stdout] 31 | if visited[(r * grid[0].len() + c) as usize] {continue;} [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `((r * grid[0].len() + c))` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unnecessary_cast [INFO] [stdout] = note: `#[warn(clippy::unnecessary_cast)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-23/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-23/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: casting to the same type is unnecessary (`usize` -> `usize`) [INFO] [stdout] --> day-12/src/part2.rs:44:24 [INFO] [stdout] | [INFO] [stdout] 44 | if visited[(r * grid[0].len() + c) as usize] {continue;} [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `((r * grid[0].len() + c))` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unnecessary_cast [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: parameter is only used in recursion [INFO] [stdout] --> day-12/src/part2.rs:10:27 [INFO] [stdout] | [INFO] [stdout] 10 | fn dfs(r: i32, c:i32, crop: char, area: &mut i32, perim: &mut i32, grid: &Vec>, visited: &mut Vec) { [INFO] [stdout] | ^^^^ help: if this is intentional, prefix it with an underscore: `_crop` [INFO] [stdout] | [INFO] [stdout] note: parameter used here [INFO] [stdout] --> day-12/src/part2.rs:36:29 [INFO] [stdout] | [INFO] [stdout] 36 | dfs(r2, c2, crop, area, perim, grid, visited); [INFO] [stdout] | ^^^^ [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#only_used_in_recursion [INFO] [stdout] = note: `#[warn(clippy::only_used_in_recursion)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-23/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-23/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: writing `&Vec` instead of `&[_]` involves a new object where a slice will do [INFO] [stdout] --> day-18/src/part1.rs:24:24 [INFO] [stdout] | [INFO] [stdout] 24 | fn find_min_cost(grid: &Vec>, start: (i32, i32), goal: (i32,i32)) -> Option { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#ptr_arg [INFO] [stdout] = note: `#[warn(clippy::ptr_arg)]` on by default [INFO] [stdout] help: change this to [INFO] [stdout] | [INFO] [stdout] 24 - fn find_min_cost(grid: &Vec>, start: (i32, i32), goal: (i32,i32)) -> Option { [INFO] [stdout] 24 + fn find_min_cost(grid: &[Vec], start: (i32, i32), goal: (i32,i32)) -> Option { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: writing `&Vec` instead of `&[_]` involves a new object where a slice will do [INFO] [stdout] --> day-18/src/part2.rs:24:24 [INFO] [stdout] | [INFO] [stdout] 24 | fn find_min_cost(grid: &Vec>, start: (i32, i32), goal: (i32,i32)) -> Option { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#ptr_arg [INFO] [stdout] help: change this to [INFO] [stdout] | [INFO] [stdout] 24 - fn find_min_cost(grid: &Vec>, start: (i32, i32), goal: (i32,i32)) -> Option { [INFO] [stdout] 24 + fn find_min_cost(grid: &[Vec], start: (i32, i32), goal: (i32,i32)) -> Option { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-04/src/bin/part2.rs:6:18 [INFO] [stdout] | [INFO] [stdout] 6 | let result = time_snippet!(process("day-04/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-09/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-09/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-16/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-16/input1.txt").unwrap()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-09/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-09/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-01/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-01/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-18/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-18/input1.txt", (70,70))); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-12/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-12/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-08/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-08/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-12/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-12/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-21/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-21/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-16/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-16/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-08/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-08/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-04/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-04/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-01/src/bin/part2.rs:6:18 [INFO] [stdout] | [INFO] [stdout] 6 | let result = time_snippet!(process("day-01/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-05/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-05/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-07/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-07/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-21/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-21/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-18/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-18/input1.txt", 1024, (70,70))); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-05/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-05/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-14/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-14/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-15/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-15/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-19/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-19/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-06/src/bin/part2.rs:6:18 [INFO] [stdout] | [INFO] [stdout] 6 | let result = time_snippet!(process("day-06/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-15/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-15/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-06/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-06/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-03/src/bin/part2.rs:6:18 [INFO] [stdout] | [INFO] [stdout] 6 | let result = time_snippet!(process("day-03/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-19/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-19/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-13/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-13/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-13/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-13/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-22/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-22/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-22/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-22/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-17/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-20/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-20/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-10/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-10/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-02/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-02/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-20/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-20/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-17/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-02/src/bin/part2.rs:6:18 [INFO] [stdout] | [INFO] [stdout] 6 | let result = time_snippet!(process("day-02/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-10/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-10/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking divan v0.1.17 [INFO] [stderr] Compiling darling_macro v0.20.10 [INFO] [stderr] Checking thiserror v1.0.69 [INFO] [stderr] Compiling darling v0.20.10 [INFO] [stderr] Compiling cached_proc_macro v0.23.0 [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-20/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-20/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-06/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-06/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-23/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-23/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-16/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-16/input1.txt").unwrap()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-18/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-18/input1.txt", 1024, (70,70))); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-03/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-03/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-15/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-15/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-07/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-07/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is used to index `grid` [INFO] [stdout] --> day-20/src/part1.rs:8:18 [INFO] [stdout] | [INFO] [stdout] 8 | for j in 0..grid[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] = note: `#[warn(clippy::needless_range_loop)]` on by default [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 8 - for j in 0..grid[0].len() { [INFO] [stdout] 8 + for (j, ) in grid.iter().enumerate().take(grid[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is used to index `grid` [INFO] [stdout] --> day-20/src/part2.rs:8:18 [INFO] [stdout] | [INFO] [stdout] 8 | for j in 0..grid[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 8 - for j in 0..grid[0].len() { [INFO] [stdout] 8 + for (j, ) in grid.iter().enumerate().take(grid[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: writing `&Vec` instead of `&[_]` involves a new object where a slice will do [INFO] [stdout] --> day-18/src/part1.rs:24:24 [INFO] [stdout] | [INFO] [stdout] 24 | fn find_min_cost(grid: &Vec>, start: (i32, i32), goal: (i32,i32)) -> Option { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#ptr_arg [INFO] [stdout] = note: `#[warn(clippy::ptr_arg)]` on by default [INFO] [stdout] help: change this to [INFO] [stdout] | [INFO] [stdout] 24 - fn find_min_cost(grid: &Vec>, start: (i32, i32), goal: (i32,i32)) -> Option { [INFO] [stdout] 24 + fn find_min_cost(grid: &[Vec], start: (i32, i32), goal: (i32,i32)) -> Option { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: writing `&Vec` instead of `&[_]` involves a new object where a slice will do [INFO] [stdout] --> day-18/src/part2.rs:24:24 [INFO] [stdout] | [INFO] [stdout] 24 | fn find_min_cost(grid: &Vec>, start: (i32, i32), goal: (i32,i32)) -> Option { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#ptr_arg [INFO] [stdout] help: change this to [INFO] [stdout] | [INFO] [stdout] 24 - fn find_min_cost(grid: &Vec>, start: (i32, i32), goal: (i32,i32)) -> Option { [INFO] [stdout] 24 + fn find_min_cost(grid: &[Vec], start: (i32, i32), goal: (i32,i32)) -> Option { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this boolean expression can be simplified [INFO] [stdout] --> day-10/src/part1.rs:8:12 [INFO] [stdout] | [INFO] [stdout] 8 | if !(0<=r && r day-10/src/part1.rs:14:29 [INFO] [stdout] | [INFO] [stdout] 14 | dfs(r+1, c, next+1, &grid, visited) + dfs(r-1, c, next+1, &grid, visited) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] = note: `#[warn(clippy::needless_borrow)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this expression creates a reference which is immediately dereferenced by the compiler [INFO] [stdout] --> day-10/src/part1.rs:14:67 [INFO] [stdout] | [INFO] [stdout] 14 | dfs(r+1, c, next+1, &grid, visited) + dfs(r-1, c, next+1, &grid, visited) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this expression creates a reference which is immediately dereferenced by the compiler [INFO] [stdout] --> day-10/src/part1.rs:15:39 [INFO] [stdout] | [INFO] [stdout] 15 | + dfs(r, c+1, next+1, &grid, visited) + dfs(r, c-1, next+1, &grid, visited) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this expression creates a reference which is immediately dereferenced by the compiler [INFO] [stdout] --> day-10/src/part1.rs:15:77 [INFO] [stdout] | [INFO] [stdout] 15 | + dfs(r, c+1, next+1, &grid, visited) + dfs(r, c-1, next+1, &grid, visited) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this boolean expression can be simplified [INFO] [stdout] --> day-10/src/part2.rs:8:12 [INFO] [stdout] | [INFO] [stdout] 8 | if !(0<=r && r day-10/src/part2.rs:13:29 [INFO] [stdout] | [INFO] [stdout] 13 | dfs(r+1, c, next+1, &grid) + dfs(r-1, c, next+1, &grid) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this expression creates a reference which is immediately dereferenced by the compiler [INFO] [stdout] --> day-10/src/part2.rs:13:58 [INFO] [stdout] | [INFO] [stdout] 13 | dfs(r+1, c, next+1, &grid) + dfs(r-1, c, next+1, &grid) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this expression creates a reference which is immediately dereferenced by the compiler [INFO] [stdout] --> day-10/src/part2.rs:14:39 [INFO] [stdout] | [INFO] [stdout] 14 | + dfs(r, c+1, next+1, &grid) + dfs(r, c-1, next+1, &grid) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this expression creates a reference which is immediately dereferenced by the compiler [INFO] [stdout] --> day-10/src/part2.rs:14:68 [INFO] [stdout] | [INFO] [stdout] 14 | + dfs(r, c+1, next+1, &grid) + dfs(r, c-1, next+1, &grid) [INFO] [stdout] | ^^^^^ help: change this to: `grid` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_borrow [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-03/src/bin/part2.rs:6:18 [INFO] [stdout] | [INFO] [stdout] 6 | let result = time_snippet!(process("day-03/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: writing `&Vec` instead of `&[_]` involves a new object where a slice will do [INFO] [stdout] --> day-21/src/part1.rs:4:25 [INFO] [stdout] | [INFO] [stdout] 4 | fn get_sequence(keypad: &Vec>) -> HashMap::<(char,char), Vec> { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#ptr_arg [INFO] [stdout] = note: `#[warn(clippy::ptr_arg)]` on by default [INFO] [stdout] help: change this to [INFO] [stdout] | [INFO] [stdout] 4 - fn get_sequence(keypad: &Vec>) -> HashMap::<(char,char), Vec> { [INFO] [stdout] 4 + fn get_sequence(keypad: &[Vec]) -> HashMap::<(char,char), Vec> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `c` is used to index `keypad` [INFO] [stdout] --> day-21/src/part1.rs:7:18 [INFO] [stdout] | [INFO] [stdout] 7 | for c in 0..keypad[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] = note: `#[warn(clippy::needless_range_loop)]` on by default [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 7 - for c in 0..keypad[0].len() { [INFO] [stdout] 7 + for (c, ) in keypad.iter().enumerate().take(keypad[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: writing `&Vec` instead of `&[_]` involves a new object where a slice will do [INFO] [stdout] --> day-21/src/part2.rs:5:25 [INFO] [stdout] | [INFO] [stdout] 5 | fn get_sequence(keypad: &Vec>) -> HashMap::<(char,char), Vec> { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#ptr_arg [INFO] [stdout] help: change this to [INFO] [stdout] | [INFO] [stdout] 5 - fn get_sequence(keypad: &Vec>) -> HashMap::<(char,char), Vec> { [INFO] [stdout] 5 + fn get_sequence(keypad: &[Vec]) -> HashMap::<(char,char), Vec> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `c` is used to index `keypad` [INFO] [stdout] --> day-21/src/part2.rs:8:18 [INFO] [stdout] | [INFO] [stdout] 8 | for c in 0..keypad[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 8 - for c in 0..keypad[0].len() { [INFO] [stdout] 8 + for (c, ) in keypad.iter().enumerate().take(keypad[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unneeded `return` statement [INFO] [stdout] --> day-07/src/part1.rs:8:5 [INFO] [stdout] | [INFO] [stdout] 8 | return false; [INFO] [stdout] | ^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_return [INFO] [stdout] = note: `#[warn(clippy::needless_return)]` on by default [INFO] [stdout] help: remove `return` [INFO] [stdout] | [INFO] [stdout] 8 - return false; [INFO] [stdout] 8 + false [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: writing `&Vec` instead of `&[_]` involves a new object where a slice will do [INFO] [stdout] --> day-07/src/part1.rs:4:33 [INFO] [stdout] | [INFO] [stdout] 4 | fn can_obtain(target:u64, nums: &Vec) -> bool { [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#ptr_arg [INFO] [stdout] = note: `#[warn(clippy::ptr_arg)]` on by default [INFO] [stdout] help: change this to [INFO] [stdout] | [INFO] [stdout] 4 - fn can_obtain(target:u64, nums: &Vec) -> bool { [INFO] [stdout] 4 + fn can_obtain(target:u64, nums: &[u64]) -> bool { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unneeded `return` statement [INFO] [stdout] --> day-21/src/part2.rs:59:5 [INFO] [stdout] | [INFO] [stdout] 59 | return length; [INFO] [stdout] | ^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_return [INFO] [stdout] = note: `#[warn(clippy::needless_return)]` on by default [INFO] [stdout] help: remove `return` [INFO] [stdout] | [INFO] [stdout] 59 - return length; [INFO] [stdout] 59 + length [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manual implementation of `.is_multiple_of()` [INFO] [stdout] --> day-07/src/part1.rs:6:8 [INFO] [stdout] | [INFO] [stdout] 6 | if target % nums[nums.len()-1] == 0 && can_obtain(target / nums[nums.len()-1],&nums[..nums.len()-1].to_vec()) {return true} [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: replace with: `target.is_multiple_of(nums[nums.len()-1])` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_is_multiple_of [INFO] [stdout] = note: `#[warn(clippy::manual_is_multiple_of)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unneeded `return` statement [INFO] [stdout] --> day-07/src/part2.rs:11:5 [INFO] [stdout] | [INFO] [stdout] 11 | return false; [INFO] [stdout] | ^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_return [INFO] [stdout] help: remove `return` [INFO] [stdout] | [INFO] [stdout] 11 - return false; [INFO] [stdout] 11 + false [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: writing `&Vec` instead of `&[_]` involves a new object where a slice will do [INFO] [stdout] --> day-07/src/part2.rs:4:33 [INFO] [stdout] | [INFO] [stdout] 4 | fn can_obtain(target:u64, nums: &Vec) -> bool { [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#ptr_arg [INFO] [stdout] help: change this to [INFO] [stdout] | [INFO] [stdout] 4 - fn can_obtain(target:u64, nums: &Vec) -> bool { [INFO] [stdout] 4 + fn can_obtain(target:u64, nums: &[u64]) -> bool { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manual implementation of `.is_multiple_of()` [INFO] [stdout] --> day-07/src/part2.rs:6:8 [INFO] [stdout] | [INFO] [stdout] 6 | if target % nums[nums.len()-1] == 0 && can_obtain(target / nums[nums.len()-1],&nums[..nums.len()-1].to_vec()) {return true} [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: replace with: `target.is_multiple_of(nums[nums.len()-1])` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_is_multiple_of [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `i` is used to index `grid` [INFO] [stdout] --> day-06/src/part1.rs:14:22 [INFO] [stdout] | [INFO] [stdout] 14 | 'outer: for i in 0..rows { [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] = note: `#[warn(clippy::needless_range_loop)]` on by default [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 14 - 'outer: for i in 0..rows { [INFO] [stdout] 14 + 'outer: for (i, ) in grid.iter().enumerate().take(rows) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is used to index `grid` [INFO] [stdout] --> day-06/src/part1.rs:15:18 [INFO] [stdout] | [INFO] [stdout] 15 | for j in 0..cols { [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 15 - for j in 0..cols { [INFO] [stdout] 15 + for (j, ) in grid.iter().enumerate().take(cols) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `row` is used to index `grid` [INFO] [stdout] --> day-06/src/part2.rs:12:16 [INFO] [stdout] | [INFO] [stdout] 12 | for row in 0..H { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 12 - for row in 0..H { [INFO] [stdout] 12 + for (row, ) in grid.iter().enumerate().take(H) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `col` is used to index `grid` [INFO] [stdout] --> day-06/src/part2.rs:13:20 [INFO] [stdout] | [INFO] [stdout] 13 | for col in 0..W { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 13 - for col in 0..W { [INFO] [stdout] 13 + for (col, ) in grid.iter().enumerate().take(W) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-13/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-13/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-12/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-12/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-16/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-16/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: comparison to empty slice [INFO] [stdout] --> day-15/src/part1.rs:9:33 [INFO] [stdout] | [INFO] [stdout] 9 | let lines = lines.split(|x| x=="").collect::>(); [INFO] [stdout] | ^^^^^ help: using `is_empty` is clearer and more explicit: `x.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#comparison_to_empty [INFO] [stdout] = note: `#[warn(clippy::comparison_to_empty)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is used to index `grid` [INFO] [stdout] --> day-15/src/part1.rs:15:18 [INFO] [stdout] | [INFO] [stdout] 15 | for j in 0..grid[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] = note: `#[warn(clippy::needless_range_loop)]` on by default [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 15 - for j in 0..grid[0].len() { [INFO] [stdout] 15 + for (j, ) in grid.iter().enumerate().take(grid[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is used to index `grid` [INFO] [stdout] --> day-15/src/part1.rs:53:18 [INFO] [stdout] | [INFO] [stdout] 53 | for j in 0..grid[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 53 - for j in 0..grid[0].len() { [INFO] [stdout] 53 + for (j, ) in grid.iter().enumerate().take(grid[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: comparison to empty slice [INFO] [stdout] --> day-15/src/part2.rs:9:33 [INFO] [stdout] | [INFO] [stdout] 9 | let lines = lines.split(|x| x=="").collect::>(); [INFO] [stdout] | ^^^^^ help: using `is_empty` is clearer and more explicit: `x.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#comparison_to_empty [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is only used to index `grid` [INFO] [stdout] --> day-15/src/part2.rs:15:18 [INFO] [stdout] | [INFO] [stdout] 15 | for j in 0..grid[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator [INFO] [stdout] | [INFO] [stdout] 15 - for j in 0..grid[0].len() { [INFO] [stdout] 15 + for in grid.iter().take(grid[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is used to index `grid_new` [INFO] [stdout] --> day-15/src/part2.rs:36:18 [INFO] [stdout] | [INFO] [stdout] 36 | for j in 0..grid_new[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 36 - for j in 0..grid_new[0].len() { [INFO] [stdout] 36 + for (j, ) in grid_new.iter().enumerate().take(grid_new[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is used to index `grid_new` [INFO] [stdout] --> day-15/src/part2.rs:88:18 [INFO] [stdout] | [INFO] [stdout] 88 | for j in 0..grid_new[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 88 - for j in 0..grid_new[0].len() { [INFO] [stdout] 88 + for (j, ) in grid_new.iter().enumerate().take(grid_new[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-01/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-01/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: usage of a legacy numeric constant [INFO] [stdout] --> day-14/src/part2.rs:9:22 [INFO] [stdout] | [INFO] [stdout] 9 | let mut min_sf = std::i32::MAX; [INFO] [stdout] | ^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#legacy_numeric_constants [INFO] [stdout] = note: `#[warn(clippy::legacy_numeric_constants)]` on by default [INFO] [stdout] help: use the associated constant instead [INFO] [stdout] | [INFO] [stdout] 9 - let mut min_sf = std::i32::MAX; [INFO] [stdout] 9 + let mut min_sf = i32::MAX; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-19/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-19/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-15/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-15/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-14/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-14/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-06/src/bin/part2.rs:6:18 [INFO] [stdout] | [INFO] [stdout] 6 | let result = time_snippet!(process("day-06/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: comparison to empty slice [INFO] [stdout] --> day-13/src/part1.rs:10:35 [INFO] [stdout] | [INFO] [stdout] 10 | let lines = binding.split(|x| x=="").collect::>(); [INFO] [stdout] | ^^^^^ help: using `is_empty` is clearer and more explicit: `x.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#comparison_to_empty [INFO] [stdout] = note: `#[warn(clippy::comparison_to_empty)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-19/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-19/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-04/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-04/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: comparison to empty slice [INFO] [stdout] --> day-13/src/part2.rs:10:35 [INFO] [stdout] | [INFO] [stdout] 10 | let lines = binding.split(|x| x=="").collect::>(); [INFO] [stdout] | ^^^^^ help: using `is_empty` is clearer and more explicit: `x.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#comparison_to_empty [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-17/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-05/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-05/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `col` is used to index `grid` [INFO] [stdout] --> day-16/src/part1.rs:33:20 [INFO] [stdout] | [INFO] [stdout] 33 | for col in 0..grid[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] = note: `#[warn(clippy::needless_range_loop)]` on by default [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 33 - for col in 0..grid[0].len() { [INFO] [stdout] 33 + for (col, ) in grid.iter().enumerate().take(grid[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-21/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-21/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `col` is used to index `grid` [INFO] [stdout] --> day-16/src/part2.rs:33:20 [INFO] [stdout] | [INFO] [stdout] 33 | for col in 0..grid[0].len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator and enumerate() [INFO] [stdout] | [INFO] [stdout] 33 - for col in 0..grid[0].len() { [INFO] [stdout] 33 + for (col, ) in grid.iter().enumerate().take(grid[0].len()) { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: very complex type used. Consider factoring parts into `type` definitions [INFO] [stdout] --> day-16/src/part2.rs:45:24 [INFO] [stdout] | [INFO] [stdout] 45 | let mut backtrack: HashMap<(usize, usize, usize), HashSet<(usize, usize, usize)>> = HashMap::new(); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#type_complexity [INFO] [stdout] = note: `#[warn(clippy::type_complexity)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of `or_insert` to construct default value [INFO] [stdout] --> day-16/src/part2.rs:64:89 [INFO] [stdout] | [INFO] [stdout] 64 | backtrack.entry((next_state.pos.0, next_state.pos.1, next_state.direc)).or_insert(HashSet::new()).clear(); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `or_default()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unwrap_or_default [INFO] [stdout] = note: `#[warn(clippy::unwrap_or_default)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of `or_insert` to construct default value [INFO] [stdout] --> day-16/src/part2.rs:67:85 [INFO] [stdout] | [INFO] [stdout] 67 | ... backtrack.entry((next_state.pos.0, next_state.pos.1, next_state.direc)).or_insert(HashSet::new()).insert((pos.0, pos.1, direc)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `or_default()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unwrap_or_default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: found `.or(Some(…)).unwrap()` [INFO] [stdout] --> day-16/src/part2.rs:76:43 [INFO] [stdout] | [INFO] [stdout] 76 | for &prev in backtrack.get(&keys).or(Some(&HashSet::new())).unwrap() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `unwrap_or(&HashSet::new())` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#or_then_unwrap [INFO] [stdout] = note: `#[warn(clippy::or_then_unwrap)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-17/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-01/src/bin/part2.rs:6:18 [INFO] [stdout] | [INFO] [stdout] 6 | let result = time_snippet!(process("day-01/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-10/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-10/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-21/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-21/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-13/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-13/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-23/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-23/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-07/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-07/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-22/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-22/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-22/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-22/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: comparison to empty slice [INFO] [stdout] --> day-19/src/lib.rs:12:33 [INFO] [stdout] | [INFO] [stdout] 12 | let lines = lines.split(|x| x == "").collect::>(); [INFO] [stdout] | ^^^^^^^ help: using `is_empty` is clearer and more explicit: `x.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#comparison_to_empty [INFO] [stdout] = note: `#[warn(clippy::comparison_to_empty)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-05/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-05/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-20/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-20/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: comparison to empty slice [INFO] [stdout] --> day-05/src/part1.rs:16:39 [INFO] [stdout] | [INFO] [stdout] 16 | let idx = lst.iter().position(|x| x=="").unwrap(); [INFO] [stdout] | ^^^^^ help: using `is_empty` is clearer and more explicit: `x.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#comparison_to_empty [INFO] [stdout] = note: `#[warn(clippy::comparison_to_empty)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: comparison to empty slice [INFO] [stdout] --> day-05/src/part2.rs:15:39 [INFO] [stdout] | [INFO] [stdout] 15 | let idx = lst.iter().position(|x| x=="").unwrap(); [INFO] [stdout] | ^^^^^ help: using `is_empty` is clearer and more explicit: `x.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#comparison_to_empty [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-02/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-02/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-10/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-10/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-09/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-09/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-08/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-08/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-08/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-08/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-14/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-14/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-18/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-18/input1.txt", (70,70))); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: casting to the same type is unnecessary (`usize` -> `usize`) [INFO] [stdout] --> day-12/src/part1.rs:31:24 [INFO] [stdout] | [INFO] [stdout] 31 | if visited[(r * grid[0].len() + c) as usize] {continue;} [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `((r * grid[0].len() + c))` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unnecessary_cast [INFO] [stdout] = note: `#[warn(clippy::unnecessary_cast)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: casting to the same type is unnecessary (`usize` -> `usize`) [INFO] [stdout] --> day-12/src/part2.rs:44:24 [INFO] [stdout] | [INFO] [stdout] 44 | if visited[(r * grid[0].len() + c) as usize] {continue;} [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `((r * grid[0].len() + c))` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unnecessary_cast [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: parameter is only used in recursion [INFO] [stdout] --> day-12/src/part2.rs:10:27 [INFO] [stdout] | [INFO] [stdout] 10 | fn dfs(r: i32, c:i32, crop: char, area: &mut i32, perim: &mut i32, grid: &Vec>, visited: &mut Vec) { [INFO] [stdout] | ^^^^ help: if this is intentional, prefix it with an underscore: `_crop` [INFO] [stdout] | [INFO] [stdout] note: parameter used here [INFO] [stdout] --> day-12/src/part2.rs:36:29 [INFO] [stdout] | [INFO] [stdout] 36 | dfs(r2, c2, crop, area, perim, grid, visited); [INFO] [stdout] | ^^^^ [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#only_used_in_recursion [INFO] [stdout] = note: `#[warn(clippy::only_used_in_recursion)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-02/src/bin/part2.rs:6:18 [INFO] [stdout] | [INFO] [stdout] 6 | let result = time_snippet!(process("day-02/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-09/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-09/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: usage of `contains_key` followed by `insert` on a `HashMap` [INFO] [stdout] --> day-22/src/part2.rs:29:13 [INFO] [stdout] | [INFO] [stdout] 29 | if !seq_to_total.contains_key(&seq) { seq_to_total.insert(seq, 0); } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `seq_to_total.entry(seq).or_insert(0);` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#map_entry [INFO] [stdout] = note: `#[warn(clippy::map_entry)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-04/src/bin/part2.rs:6:18 [INFO] [stdout] | [INFO] [stdout] 6 | let result = time_snippet!(process("day-04/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-12/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-12/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: length comparison to zero [INFO] [stdout] --> day-17/src/part2.rs:5:12 [INFO] [stdout] | [INFO] [stdout] 5 | if program.len() == 0 { return Some(ans); } [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ help: using `is_empty` is clearer and more explicit: `program.is_empty()` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#len_zero [INFO] [stdout] = note: `#[warn(clippy::len_zero)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking cached v0.54.0 [INFO] [stderr] Checking day-11 v0.1.0 (/opt/rustwide/workdir/day-11) [INFO] [stdout] warning: the loop variable `j` is only used to index `stones` [INFO] [stdout] --> day-11/src/part1.rs:8:18 [INFO] [stdout] | [INFO] [stdout] 8 | for j in 0..stones.len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] = note: `#[warn(clippy::needless_range_loop)]` on by default [INFO] [stdout] help: consider using an iterator [INFO] [stdout] | [INFO] [stdout] 8 - for j in 0..stones.len() { [INFO] [stdout] 8 + for in &stones { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manual implementation of `.is_multiple_of()` [INFO] [stdout] --> day-11/src/part1.rs:11:23 [INFO] [stdout] | [INFO] [stdout] 11 | } else if (stones[j].ilog10()+1)%2==0 { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: replace with: `(stones[j].ilog10() + 1).is_multiple_of(2)` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_is_multiple_of [INFO] [stdout] = note: `#[warn(clippy::manual_is_multiple_of)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manually reimplementing `div_ceil` [INFO] [stdout] --> day-11/src/part1.rs:12:50 [INFO] [stdout] | [INFO] [stdout] 12 | output.push(stones[j]/10_u64.pow((stones[j].ilog10()+1)/2)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ help: consider using `.div_ceil()`: `stones[j].ilog10().div_ceil(2)` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_div_ceil [INFO] [stdout] = note: `#[warn(clippy::manual_div_ceil)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manually reimplementing `div_ceil` [INFO] [stdout] --> day-11/src/part1.rs:13:50 [INFO] [stdout] | [INFO] [stdout] 13 | output.push(stones[j]%10_u64.pow((stones[j].ilog10()+1)/2)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ help: consider using `.div_ceil()`: `stones[j].ilog10().div_ceil(2)` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_div_ceil [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manual implementation of `.is_multiple_of()` [INFO] [stdout] --> day-11/src/part2.rs:13:8 [INFO] [stdout] | [INFO] [stdout] 13 | if (stone.ilog10()+1)%2==0 { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ help: replace with: `(stone.ilog10() + 1).is_multiple_of(2)` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_is_multiple_of [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manually reimplementing `div_ceil` [INFO] [stdout] --> day-11/src/part2.rs:14:20 [INFO] [stdout] | [INFO] [stdout] 14 | let half = (stone.ilog10()+1)/2; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ help: consider using `.div_ceil()`: `stone.ilog10().div_ceil(2)` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_div_ceil [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `i` is only used to index `stones` [INFO] [stdout] --> day-11/src/part2_2.rs:7:14 [INFO] [stdout] | [INFO] [stdout] 7 | for i in 0..stones.len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator [INFO] [stdout] | [INFO] [stdout] 7 - for i in 0..stones.len() { [INFO] [stdout] 7 + for in &stones { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manually reimplementing `div_ceil` [INFO] [stdout] --> day-11/src/part2_2.rs:17:43 [INFO] [stdout] | [INFO] [stdout] 17 | *new_v.entry(x/10_u64.pow((x.ilog10()+1)/2)).or_insert(0)+=count; [INFO] [stdout] | ^^^^^^^^^^^^^^^^ help: consider using `.div_ceil()`: `x.ilog10().div_ceil(2)` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_div_ceil [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manually reimplementing `div_ceil` [INFO] [stdout] --> day-11/src/part2_2.rs:18:43 [INFO] [stdout] | [INFO] [stdout] 18 | *new_v.entry(x%10_u64.pow((x.ilog10()+1)/2)).or_insert(0)+=count; [INFO] [stdout] | ^^^^^^^^^^^^^^^^ help: consider using `.div_ceil()`: `x.ilog10().div_ceil(2)` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_div_ceil [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `j` is only used to index `stones` [INFO] [stdout] --> day-11/src/part1.rs:8:18 [INFO] [stdout] | [INFO] [stdout] 8 | for j in 0..stones.len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] = note: `#[warn(clippy::needless_range_loop)]` on by default [INFO] [stdout] help: consider using an iterator [INFO] [stdout] | [INFO] [stdout] 8 - for j in 0..stones.len() { [INFO] [stdout] 8 + for in &stones { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manual implementation of `.is_multiple_of()` [INFO] [stdout] --> day-11/src/part1.rs:11:23 [INFO] [stdout] | [INFO] [stdout] 11 | } else if (stones[j].ilog10()+1)%2==0 { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: replace with: `(stones[j].ilog10() + 1).is_multiple_of(2)` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_is_multiple_of [INFO] [stdout] = note: `#[warn(clippy::manual_is_multiple_of)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manually reimplementing `div_ceil` [INFO] [stdout] --> day-11/src/part1.rs:12:50 [INFO] [stdout] | [INFO] [stdout] 12 | output.push(stones[j]/10_u64.pow((stones[j].ilog10()+1)/2)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ help: consider using `.div_ceil()`: `stones[j].ilog10().div_ceil(2)` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_div_ceil [INFO] [stdout] = note: `#[warn(clippy::manual_div_ceil)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manually reimplementing `div_ceil` [INFO] [stdout] --> day-11/src/part1.rs:13:50 [INFO] [stdout] | [INFO] [stdout] 13 | output.push(stones[j]%10_u64.pow((stones[j].ilog10()+1)/2)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ help: consider using `.div_ceil()`: `stones[j].ilog10().div_ceil(2)` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_div_ceil [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manual implementation of `.is_multiple_of()` [INFO] [stdout] --> day-11/src/part2.rs:13:8 [INFO] [stdout] | [INFO] [stdout] 13 | if (stone.ilog10()+1)%2==0 { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ help: replace with: `(stone.ilog10() + 1).is_multiple_of(2)` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_is_multiple_of [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manually reimplementing `div_ceil` [INFO] [stdout] --> day-11/src/part2.rs:14:20 [INFO] [stdout] | [INFO] [stdout] 14 | let half = (stone.ilog10()+1)/2; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ help: consider using `.div_ceil()`: `stone.ilog10().div_ceil(2)` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_div_ceil [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: called `map(..).flatten()` on `Iterator` [INFO] [stdout] --> day-11/src/lib.rs:12:11 [INFO] [stdout] | [INFO] [stdout] 12 | lines.map(|x| x.unwrap().split_whitespace().map(|x| x.parse().unwrap()).collect::>()).flatten().collect::>() [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try replacing `map` with `flat_map` and remove the `.flatten()`: `flat_map(|x| x.unwrap().split_whitespace().map(|x| x.parse().unwrap()).collect::>())` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#map_flatten [INFO] [stdout] = note: `#[warn(clippy::map_flatten)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: the loop variable `i` is only used to index `stones` [INFO] [stdout] --> day-11/src/part2_2.rs:7:14 [INFO] [stdout] | [INFO] [stdout] 7 | for i in 0..stones.len() { [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_range_loop [INFO] [stdout] help: consider using an iterator [INFO] [stdout] | [INFO] [stdout] 7 - for i in 0..stones.len() { [INFO] [stdout] 7 + for in &stones { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manually reimplementing `div_ceil` [INFO] [stdout] --> day-11/src/part2_2.rs:17:43 [INFO] [stdout] | [INFO] [stdout] 17 | *new_v.entry(x/10_u64.pow((x.ilog10()+1)/2)).or_insert(0)+=count; [INFO] [stdout] | ^^^^^^^^^^^^^^^^ help: consider using `.div_ceil()`: `x.ilog10().div_ceil(2)` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_div_ceil [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: manually reimplementing `div_ceil` [INFO] [stdout] --> day-11/src/part2_2.rs:18:43 [INFO] [stdout] | [INFO] [stdout] 18 | *new_v.entry(x%10_u64.pow((x.ilog10()+1)/2)).or_insert(0)+=count; [INFO] [stdout] | ^^^^^^^^^^^^^^^^ help: consider using `.div_ceil()`: `x.ilog10().div_ceil(2)` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_div_ceil [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: called `map(..).flatten()` on `Iterator` [INFO] [stdout] --> day-11/src/lib.rs:12:11 [INFO] [stdout] | [INFO] [stdout] 12 | lines.map(|x| x.unwrap().split_whitespace().map(|x| x.parse().unwrap()).collect::>()).flatten().collect::>() [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try replacing `map` with `flat_map` and remove the `.flatten()`: `flat_map(|x| x.unwrap().split_whitespace().map(|x| x.parse().unwrap()).collect::>())` [INFO] [stdout] | [INFO] [stdout] = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#map_flatten [INFO] [stdout] = note: `#[warn(clippy::map_flatten)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-11/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-11/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-11/src/bin/part2.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-11/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-11/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-11/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `tracing` [INFO] [stdout] --> day-11/src/bin/part1.rs:5:18 [INFO] [stdout] | [INFO] [stdout] 5 | let result = time_snippet!(process("day-11/input1.txt")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `time_snippet` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `time_snippet` may come from an old version of the `code_timing_macros` crate, try updating your dependency with `cargo update -p code_timing_macros` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `time_snippet` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 20.71s [INFO] running `Command { std: "docker" "inspect" "99fe3a542191823e4fa232c4bbaccb275091172f2e54fa21164de9443fafb4d3", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "99fe3a542191823e4fa232c4bbaccb275091172f2e54fa21164de9443fafb4d3", kill_on_drop: false }` [INFO] [stdout] 99fe3a542191823e4fa232c4bbaccb275091172f2e54fa21164de9443fafb4d3