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]>
34 lines
1.4 KiB
TOML
34 lines
1.4 KiB
TOML
# The steps of WAI's packaging extension that a GPU computes exactly, as WGSL compute
|
|
# kernels through wgpu (shown exact on Metal only; Vulkan and DX12 built, not run): the
|
|
# integer encoder's motion search, the
|
|
# sum of squared differences, and BLAKE3's chunk function. Every kernel is integer, in
|
|
# 32-bit words, so a device that runs it gives the CPU's result for every input
|
|
# (extensions/packaging.md §11.6).
|
|
#
|
|
# A SEPARATE crate with its own lockfile, as wai-ops-gpu is, so that wai-pack builds
|
|
# without wgpu by default; wai-pack's `gpu` feature is the only way it enters a pack.
|
|
[package]
|
|
name = "wai-pack-gpu"
|
|
version = "0.1.0"
|
|
edition = "2024"
|
|
license = "Apache-2.0"
|
|
publish = false
|
|
description = "WAI packaging steps on GPUs: the integer motion search, SSE and BLAKE3's chunk function as WGSL kernels through wgpu, exact in 32-bit words"
|
|
repository = "https://git.transaction.science/Transaction-Science/open-standards"
|
|
|
|
# Its own workspace and Cargo.lock.
|
|
[workspace]
|
|
|
|
[lib]
|
|
name = "wai_pack_gpu"
|
|
path = "src/lib.rs"
|
|
|
|
[dependencies]
|
|
wgpu = { version = "30.0.1", default-features = false, features = ["std", "wgsl", "metal", "vulkan", "dx12"] }
|
|
# The parent nodes of a message of several chunks are merged on the host, by the BLAKE3
|
|
# reference crate's subtree functions (`blake3::hazmat`); the device computes the chunks.
|
|
blake3 = "1"
|
|
|
|
[profile.release]
|
|
debug = false
|
|
overflow-checks = true
|