KhronosGroup / KhronosGroup/glslang
Implement fixes for built-in block member ambiguities across multiple specifications
- Dominant language
- C++
- Stars
- 3.6k
- Forks
- 989
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 31
Description
It was not always clear which built-in variables are supposed to be in which built-in block (or not at all). There were both specification issues and glslang issues related to this.
Much work was already done in glslang to address the progress in this space, and this issue is meant to help finish it all off.
Contributor guide
Research direction
Review the existing glslang work and the relevant built-in block specifications first; the issue does not identify specific files, tests, or entry points. Compare the remaining specification and implementation discrepancies, then confirm that built-in variables are assigned consistently across all affected specifications and glslang behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100