SparseElementsAttr currently models its indices and values parameters as plain AttributeValue in the generated C# surface. That preserves flexibility, but it does not capture the real semantics of the sparse COO payload.
Desired follow-up:
- introduce semantic types for the sparse indices and sparse values payloads
- update the builtin prelude overlay so SparseElementsAttr uses those richer types
- keep the behavior aligned with MLIR's sparse elements assembly and validation rules
- add tests that confirm the generator emits the new semantic types
If the repo does not yet have the right abstraction for these payloads, add it in the runtime/semantic layer first and then wire the prelude overlay to it.
SparseElementsAttr currently models its indices and values parameters as plain AttributeValue in the generated C# surface. That preserves flexibility, but it does not capture the real semantics of the sparse COO payload.
Desired follow-up:
If the repo does not yet have the right abstraction for these payloads, add it in the runtime/semantic layer first and then wire the prelude overlay to it.