FA-100449 / Sparse tensor canonicalization / Member archive
Sparse tensor: COO entries retain input order instead of row-major canonical order · case 04
COO entries retain input order instead of row-major canonical order.
Case contract
Return entries sorted by row then column; coordinates are unique and values are preserved.
Why this case matters
A small offline sparse-array operation has explicit coordinate and storage semantics.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| reverse coordinates | [[1, 0, 4], [0, 2, 4]] | [[0, 2, 4], [1, 0, 4]] | Failed |
MEMBER ARCHIVE
The complete case is available to members.
This record includes three runnable implementations, regression fixtures, execution results, and source hashes.
Member access is invitation-based. Sign in with your invited account to inspect the sources.
Sign in to the archive ↗