reference-data-type-not-supported-pre-sm610
Status: stub. The full-length analysis is queued for a v1.0.x patch release per ADR 0018, section 5, criterion #6. The companion rule page at docs/rules/reference-data-type-not-supported-pre-sm610.md contains the canonical detection logic + GPU reasoning.
TL;DR
Reference data types are not yet shipped retail. Source compiled with the proposal-0006 syntax against SM 6.9 toolchains may compile-error or produce wrong code. The rule warns prospectively until the proposal ships.
What the rule fires on
<qual> ref <type> parameter syntax (matching HLSL Specs proposal 0006, under-review) on a translation unit targeting SM 6.9 or older.
See the What it detects section of the rule page for the full pattern definition.
Why it matters
The full GPU-mechanism analysis lives in the Why it matters on a GPU section of the companion rule page.
Examples
The bad / good code snippets are kept canonical on the rule page; see reference-data-type-not-supported-pre-sm610.md -> Examples.
See also
- Rule page -- canonical reference + change log.
- sm6_10 overview -- broader context.
- ADR 0018 -- v1.0 readiness plan.
This is a v1.0-ship stub. Full analysis pending; track issue link TBD.