You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`src/property_mask.rs:426` — `clippy::unusual_byte_groupings` — `0b11111_1000` → `0b1_1111_1000` (regrouped into nibbles per clippy's own suggestion; value unchanged, still asserting the same bit pattern).
20
+
-`src/bitwise.rs:637` — `clippy::identity_op` — `assert_eq!(super::popcount_batch_u64(&words), 64 + 0 + 32)` had a no-op `+ 0`. Replaced with the literal `96` and kept the per-word breakdown as a comment (`// per-word contributions: 64 + 0 + 32`) so the documentational intent survives.
21
+
-`src/palette_codec.rs:810` — `clippy::needless_range_loop` in `test_bedrock_pack_section` — `for i in 0..4096 { states[i] = (i % 4) as u16; }` → `for (i, state) in states.iter_mut().enumerate() { *state = (i % 4) as u16; }`. Purely mechanical (index only used for indexing + the `% 4` value); no semantic change.
22
+
23
+
Re-run: clean (`Finished` in 36.14s).
24
+
25
+
## Pass 3 — `cargo fmt -p ndarray`
26
+
27
+
Applied. Reformatted only the touched hunks (rustfmt collapsed the shortened `next()` bodies and normalized the byte-grouping/comment line spacing). No behavioural diff beyond formatting.
28
+
29
+
## Nothing skipped
30
+
31
+
No `src/simd_*.rs` files were touched — none of the flagged lints landed there. No `unsafe` blocks were touched (none of the fixes were near unsafe code). No public API signatures changed.
- No `cargo test` run (disk guard tripped — see below).
39
+
40
+
## Disk guard note
41
+
42
+
Free space on `/home/user` dropped from 5.7 GB → 5.3 GB → **4.2 GB** over the course of this run (crossing the 5 GB floor right after the `cargo fmt` invocation, which had itself been preceded by a compliant 5.3 GB check). Per the hard rule I stopped immediately after `cargo fmt` and did **not** run any further cargo invocations (no targeted `cargo test`, no additional clippy passes). All fixes above are comment/mechanical-only changes (`.clone()?` collapse, digit regrouping, literal substitution, `iter_mut().enumerate()`), so behavioural risk is low, but the orchestrator should re-run `cargo test -p ndarray` centrally once disk space is confirmed healthy.
0 commit comments