From 816218549b1f73bcd9294f9937e953cabc9a66a8 Mon Sep 17 00:00:00 2001 From: Stefanie Jane Date: Tue, 3 Nov 2026 12:01:00 -0800 Subject: [PATCH] build(lints): allow clippy::assert_is_empty from Rust 1.99 Rust 1.99.1 added assert_is_empty to the pedantic group, which this crate denies, so CI broke on ten existing `assert!(v.is_empty())` checks without any code change. Clippy's suggested fix rewrites them as `assert_eq!(v, [] as [Type; 0])`, which is harder to read, so the lint joins the other pragmatic style allowances. Co-Authored-By: Nova (Claude Opus 5.5) --- Cargo.toml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Cargo.toml b/Cargo.toml index 144e5e9..3778d02 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -104,6 +104,9 @@ missing_safety_doc = { level = "allow", priority = 20 } module_name_repetitions = { level = "allow", priority = 21 } significant_drop_tightening = { level = "allow", priority = 21 } must_use_candidate = { level = "allow", priority = 21 } +# Rust 1.99 added this to pedantic; its fix trades `assert!(v.is_empty())` for +# `assert_eq!(v, [] as [Type; 0])`, which reads worse in tests +assert_is_empty = { level = "allow", priority = 21 } # Numeric casting and conversion warnings cast_precision_loss = { level = "warn", priority = 22 }