Clarify naming conventions for opaque types in NSDI.100 #370
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update 'Name' requirements to indicate it should be mangled in an implementation-defined manner to avoid clashes with user-defined names.
bashbaug
approved these changes
Nov 19, 2025
Collaborator
bashbaug
left a comment
bashbaug
left a comment
There was a problem hiding this comment.
Merging as discussed in the November 19th teleconference.
dnovillo
added a commit
to dnovillo/SPIRV-Registry
that referenced
this pull request
Nov 19, 2025
…on. (KhronosGroup#370) Update 'Name' requirements to indicate it should be mangled in an implementation-defined manner to avoid clashes with user-defined names.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This stops the NSDI.100 spec from mandating a specific mangling for opaque types. It updates 'Name' requirements to indicate it should be mangled in an implementation-defined manner to avoid clashes with user-defined names.
This should help address issues like KhronosGroup/glslang#4063