Skip to content

rules: explicitly prohibit handwritten contraction kernels #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shinaoka merged 1 commit into from
Oct 31, 2026
Merged

rules: explicitly prohibit handwritten contraction kernels #31

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions rules/rust/performance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,15 @@
- No hidden row-major compatibility shims or silent row-major round-trips.
- Use the owning backend/linalg abstraction for GEMM, einsum, decompositions,
and solves. Do not reimplement kernels in downstream layers.

Contractions, GEMM, decompositions and solves must use the owning abstraction
(`einsum_tensors`, `tcontract`, `tlinalg`, or the backend provider); never replace
them with a repository-local inner scalar-accumulate loop. Handwritten kernels
bypass the tuned path, threading/SIMD policy and the abstractions' numeric
contract. If a loop genuinely cannot be expressed through the abstraction, put
`// contraction-kernel-ok: <reason>` immediately above that loop and explain the
exception in the PR description.

- When integrating faer, BLAS, LAPACK, or CUDA libraries, keep packing and ABI
copies at explicit boundaries and reuse scratch where possible.
- A work copy's leading dimension must not be a multiple of 1 KiB. A column
Expand Down
Loading