d14f583d92
The repository tracks the latest stable Rust, pinned at the root. A
`rust-version` key states a *floor* -- the oldest toolchain a crate supports --
which is a different promise, and one this repository does not make. It also
said 1.97 while the pin was 1.98.0 and nothing verified it, so it was a claim in
the wrong direction and unchecked in both.
So it goes, everywhere:
59 rust-version = "1.97" (workspace and package declarations)
417 rust-version.workspace = true (members inheriting them)
476 files, 476 deletions, 0 insertions
The 417 are why this is not the sixty-file change it looks like from a grep for
the value. A member inheriting a key that no longer exists does not fall back to
a default -- its manifest stops resolving. Removing the declarations without the
inherits would have broken every workspace that has members.
Deliberately untouched: `joule-code-rs/vendor/wtransport/Cargo.toml`. That is a
vendored third-party crate declaring a floor about itself, not about us, and our
pin is above it. Editing vendored source to satisfy our own policy would make
the copy diverge from upstream for no benefit.
Verified rather than assumed:
- all 493 `Cargo.toml` files in the tree parse (`tomllib`)
- `cargo metadata --no-deps --locked` resolves on `joule-code-rs`, `wai-rs`,
`openpay`, `mesh-rs`, `sandbox-rs` and `jcp-rs` -- the check that actually
exercises workspace inheritance, which a TOML parse does not
- no `Cargo.lock` changed; `rust-version` is not lockfile state
`wai/wai-verify/Cargo.toml` already carried a comment saying it omits
`rust-version` on purpose, so this makes the rest of the tree agree with the one
crate that had already decided.
What this gives up, stated plainly: cargo can no longer greet an older
toolchain with "requires rustc 1.97" and will instead fail wherever the code
first needs something newer. That is the cost of not maintaining a floor, and
it is the right cost when the floor was fiction.
Co-Authored-By: Claude Opus 5 <[email protected]>
31 lines
1.3 KiB
TOML
31 lines
1.3 KiB
TOML
# Time and energy of the integer decoders with their graphs on the CPU and on a GPU
|
|
# (wai-rs `ops_gpu`), per capability, on the committed vectors.
|
|
#
|
|
# A SEPARATE crate with its own lockfile, as quantum-meter is: the energy sources it reads
|
|
# (this process's CPU and GPU counters on macOS, RAPL package energy and the NVIDIA
|
|
# driver's cumulative energy counter on Linux) belong with the tool that reads them, and
|
|
# never compile in wai-rs's own builds or tests.
|
|
[package]
|
|
name = "ops-gpu-bench"
|
|
version = "0.0.0"
|
|
edition = "2024"
|
|
license = "Apache-2.0"
|
|
publish = false
|
|
|
|
[dependencies]
|
|
wai = { path = "../../wai-rs", default-features = false, features = ["ops_gpu", "video_int", "audio_int", "splat_int", "world_int"] }
|
|
wai-ops = { path = "../../wai-ops" }
|
|
serde_json = "1"
|
|
|
|
# On macOS on Apple Silicon: this process's CPU energy and its share of the GPU rail
|
|
# (IOReport), the span meter quantum-meter uses.
|
|
[target.'cfg(target_os = "macos")'.dependencies]
|
|
jouleclaw-energy = { path = "../../../jouleclaw/jouleclaw-rs/crates/jouleclaw-energy", default-features = false, features = ["ioreport"] }
|
|
|
|
# On Linux: the NVIDIA driver's library is opened at run time, so a host without it
|
|
# builds and reports no GPU energy.
|
|
[target.'cfg(target_os = "linux")'.dependencies]
|
|
libc = "0.2"
|
|
|
|
[profile.release]
|
|
debug = false
|