crypto/mlkem — validation proof
Go’s own crypto/mlkem test suite, converted to C# by go2cs, built against the converted standard
library, run under the Go-semantics test host, and compared verdict for verdict against a clean
go test -json baseline of the same sources. This page is generated by the converter from that
comparison — it is the evidence behind the crypto/mlkem row in
Validated Test Packages.
Validated 2026-10-25 · converter b5fc1294d
8 matched · 0 disclosed — Go 1.26.10, windows/amd64, converted package
src/core/crypto/mlkem.
Measured at Release (tiered JIT off), oracle go version go1.26.10 windows/amd64.
Verdicts
| Test | go test |
go2cs |
|---|---|---|
TestAccumulated |
pass | pass |
TestBadLengths |
pass | pass |
TestBadLengths/1024 |
pass | pass |
TestBadLengths/768 |
pass | pass |
TestConstantSizes |
pass | pass |
TestRoundTrip |
pass | pass |
TestRoundTrip/1024 |
pass | pass |
TestRoundTrip/768 |
pass | pass |
Excluded declarations
Declarations filtered from both sides of the comparison, and therefore not claimed above:
Benchmark, Fuzz and Example declarations the converted host does not execute, plus any
test requiring a capability the managed runtime does not provide — a testing member the host
has not implemented, or a platform behavior it provably cannot reproduce. Each is named with
the capability it needs.
- BenchmarkDecaps (benchmark): benchmark execution is deferred to Phase 4D
- BenchmarkEncaps (benchmark): benchmark execution is deferred to Phase 4D
- BenchmarkKeyGen (benchmark): benchmark execution is deferred to Phase 4D
- BenchmarkRoundTrip (benchmark): benchmark execution is deferred to Phase 4D
- Example (example): example execution is deferred to Phase 4D