KhronosGroup / KhronosGroup/GLSL
should samplerND(samplerND, sampler) be added?
- Dominant language
- JavaScript
- Stars
- 458
- Forks
- 114
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
SPIR-V has language that allows to extract the OpTypeImage via OpImage from OpTypeSampledImage, which allows the recombination to a new OpTypeSampledImage with a different OpTypeSampler
therefore shouldn't the language also allow samplerND constructors from existing combined samplers?
samplerND(samplerND, sampler)
Contributor guide
Research direction
Start by reading the GLSL specification and the issue's SPIR-V references to OpTypeImage, OpImage, and OpTypeSampledImage. Determine where samplerND constructors are specified and whether the proposed samplerND(samplerND, sampler) behavior fits the existing language rules; done means the specification decision and any required wording are documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100