Skip to content

Conversation

@alelenv
Copy link
Contributor

@alelenv alelenv commented Jan 23, 2026

GLSL spec here : KhronosGroup/GLSL#304

Glslang only change, no changes required for SPIRV Headers / Tools

@arcady-lunarg
Copy link
Contributor

Since the spec specifically calls out (vec3) (1, 2, 3) as something that's likely to give undesirable results, would it be possible to warn in that case? That seems like it would be a good way to let users know that their code is probably not doing what they want.

@arcady-lunarg arcady-lunarg self-requested a review January 23, 2026 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants