IOReport meters: the two clippy warnings each macOS reader carried #244
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/ioreport-meter-lints"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What was wrong
Three crates carry the same IOReport energy reader: proof-cascade, eoc-meter and jouleclaw-energy. Clippy warned twice in each of them. The code only builds on macOS, so a Linux run never sees these warnings.
duplicated_attributesfires on the emptyexternblock that links IOReport, IOKit and CoreFoundation. Two of those links usekind = "framework", and the lint reads the repeated key as a duplicate. They are three distinct libraries, so the lint is allowed with that reason, as jcp-energy has done since June.manual_c_str_literals:b"IOReportChannels\0"becomesc"IOReportChannels", the form these files already use for their other keys. The pointer passed toCFStringCreateWithCStringis unchanged.Checked
A macOS sweep of every workspace (
cargo clippy --all-targets --keep-going, on main with #241 merged in) found no deny-level error in any workspace. The 6 warnings here were the only instances of either lint.On the build host, after the change:
--features ioreport) 129.No file overlaps #241.
🤖 Generated with Claude Code