The semantics of strides in IndexSequence is inconsistent
Open
- Dominant language
- Python
- Stars
- 59
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
Index sequence analysis propagating from MMA treats this as per-dimension stride, propagating from Writes or Reductions treats this as torch-style stride for linearized memory storage. Switching the latter to be 1 everywhere, which would be consistent with the per-dimension interpretation, doesn't break any integration tests: #954.
Contributor guide
Assessment
This issue has not been assessed yet.