Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enforce best practices for guarding enums #370

Closed
wants to merge 2 commits into from

Conversation

dneto0
Copy link
Contributor

@dneto0 dneto0 commented Aug 4, 2023

Enforce best practices for guarding enums

An enum introduced by an extension (that is not in a core SPIR-V
version) is either:
- a capability, or
- not a capability, but guarded by a capability and not guarded by an extension.

Allow cases that have already landed, with an allow-list.

Fixes: #278

Builds on #369

@dneto0 dneto0 requested a review from alan-baker August 4, 2023 19:50
An enum introduced by an extension (that is not in a core SPIR-V
version) is either:
- a capability, or
- not a capability, but guarded by a capability and not guarded by an extension.

Allow cases that have already landed, with an allow-list.

Fixes: KhronosGroup#278
@dneto0
Copy link
Contributor Author

dneto0 commented Aug 10, 2023

Folded into #369

@dneto0 dneto0 closed this Aug 10, 2023
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.

CI headers check should ensure non-capability enums are guarded by capability, not by extension
1 participant