Skip to content

fix: satisfy current Clippy lint for brightness icon - #189

Merged
FoOcean merged 1 commit into
masterfrom
codex/fix-1.3.9-ci-clippy
Sep 23, 2026
Merged

FoOcean merged 1 commit into
masterfrom
codex/fix-1.3.9-ci-clippy

Conversation

@FoOcean

@FoOcean FoOcean commented Sep 23, 2026

Copy link
Copy Markdown
Collaborator

Pre-submission checklist

  • I have read CONTRIBUTING.md and completed the required checks
  • Local and CI checks pass (local checks pass; CI is pending)
  • I have completed a self-review
  • I confirm that I haven't read the checkboxes and just ticked them all

Change type (select one)

  • feat New feature
  • fix Bug fix
  • docs Documentation or templates
  • style Formatting with no behavior change
  • refactor Code change that neither fixes a bug nor adds a feature
  • perf Performance improvement
  • test Test-related change
  • chore Build, CI, dependency, or tooling change
  • revert Revert
  • security Security fix

Scope (select all that apply)

  • Application core
  • UI style or layout
  • Application behavior
  • Dependency changes
  • Plugin API
  • CI/CD configuration
  • Documentation
  • Other (describe below)

Related issues

Follow-up to #188.


Description

Summary

Use the current Clippy-recommended four-byte chunk iteration for brightness icon pixels.

Motivation and context

The GitHub Actions runner uses Rust 1.98, which rejects chunks_exact_mut(4) with -D warnings. The locally installed Rust 1.96 did not flag it, so this one-line compatibility fix is needed before the 1.3.9 release workflow runs.

Changes

  • Replace chunks_exact_mut(4) with as_chunks_mut::<4>().0 in the brightness icon conversion loop.

UI changes

No visible UI changes.

Validation: cargo fmt --all, cargo clippy --workspace --offline -- -D warnings, and cargo build --release --offline passed locally. The prior GitHub Actions log showed only the Rust 1.98 lint error addressed here.

Signed-off-by: FoOcean <foocean@outlook.com>
@FoOcean
FoOcean merged commit 0fcb3c1 into master Sep 23, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant