Fix stable Rust chunk lint - #400
Conversation
|
Warning Review limit reached
Next review available in: 44 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Comment |
Merging this PR will not alter performance
Comparing Footnotes
|
What changed
chunks_exact/chunks_exact_mutloops withas_chunks/as_chunks_mutin the Rust kernels, raster, and tile paths.Why
Rust 1.96.1 enables
clippy::chunks_exact_to_as_chunks, and the repository promotes warnings to errors. The floating stable CI toolchain therefore rejected the existing loops even though their behavior was correct.Impact
The required stable-Rust Clippy gate passes again without changing the data-path semantics.
Validation
cargo clippy --all-targets -- -D warningscargo test— 137 passedFixes #392