emilk opened a new pull request, #24465:
URL: https://github.com/apache/datafusion/pull/24465

   ## Which issue does this PR close?
   
   - Part of #18467.
   
   ## Rationale for this change
   
   We have been enabling `clippy::pedantic` lints one at a time, which means new
   pedantic lints land silently disabled on every toolchain bump. Opting out
   instead of opting in flips that default: a new lint is enforced unless we
   say otherwise.
   
   ## What changes are included in this PR?
   
   Two commits, `Cargo.toml` only.
   
   1. Enable `pedantic` as a group. 58 explicit opt-ins it now covers are
      removed. The 72 lints that still fire are set to `"allow"`, each with its
      hit count so we can see what fixing it would cost. The other 71 are
      enforced, 13 of them for the first time: `copy_iterator`,
      `doc_broken_link`, `maybe_infinite_iter`, `naive_bytecount`,
      `no_mangle_with_rust_abi`, `nonminimal_bool`, `overly_complex_bool_expr`,
      `ptr_offset_by_literal`, `range_minus_one`, `ref_binding_to_reference`,
      `unnecessary_join`, `unsafe_derive_deserialize`, `verbose_bit_mask`.
   2. Enable `all` as a group. Nothing new fires, and it makes one explicit
      opt-in redundant (`unnecessary_lazy_evaluations`).
   
   Note the hit counts are toolchain-specific: lints move between groups on a
   bump, so a toolchain bump may need new opt-outs.
   
   ## Are these changes tested?
   
   `cargo clippy --workspace --all-targets --all-features` reports no warnings.
   No code changes, so existing tests cover behavior.
   
   ## Are there any user-facing changes?
   
   No.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to