microsoft / microsoft/DirectXShaderCompiler
[SM6.10] Use consistent naming for ComponentType parameters
@V-FEXrt is already working on this.
Since Jul 22, 2026.
- Dominant language
- C++
- Stars
- 3.7k
- Forks
- 900
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 44
Description
Follow up from #8299:
"I found that inconsistent naming for typename ...Ty vs. ComponentEnum ...Ty made this harder to read and review.
Matrix uses ComponentEnum MatrixDT, which helps, but DT isn't a convention used elsewhere, nor does it match the naming ComponentType which has a long history in HLSL and would better match the ComponentEnum naming.
Could we standardize on naming things with CT when referring to a ComponentType specified by the ComponentEnum and Ty when referring to an actual native type?"
Originally posted by @tex3d in https://github.com/microsoft/DirectXShaderCompiler/pull/8299#pullrequestreview-4040114842
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.