Transaction Science
fba729ce7b
jcp-energy: clippy-clean on Linux, with and without nvml
...
- `FabricMeter::readable` and `FabricMeter::measure` built their vector
`mut` on every platform and pushed to it only on macOS, so Linux reported
two unused `mut`s. Each now has a macOS body that builds and returns the
vector, and a body for everywhere else that returns it empty. The behaviour
is the same on both.
- `FabricSource::has_backend`: with `nvml` on, its match folded to a
`matches!` (match_like_matches_macro). It is written as one, with the nvml
arm still gated on the feature.
- tests/nvml_hardware.rs: the `nvidia-smi` power triple is the oracle's
`SmiPower` alias (type_complexity under `--features nvml`).
Clippy -D warnings is clean on Linux (default, nvml) and in the macOS lint
step (jcp-energy, jcp-gateway). Tests pass: Linux default (68) and nvml (70),
macOS lib (128).
Co-Authored-By: Claude Opus 5.5 <[email protected] >
2026-11-05 10:21:43 -05:00
..
jcp-a2a
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-action-receipt
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-bridge
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-channel
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-cite
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-cli
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-conformance
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-efficiency
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-energy
jcp-energy: clippy-clean on Linux, with and without nvml
2026-11-05 10:21:43 -05:00
jcp-flow
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-gateway
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-grant
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-intercept
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-orchestrate
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-policy
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-prompt
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-receipt
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-runtime
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-schema
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-threshold
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-trace
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-wire
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00
jcp-x402
Cargo: no minimum-supported-version floor, because the policy is latest stable
2026-11-03 17:42:20 -05:00