Repository navigation
refactor: clarify Vulkan query compatibility workarounds - #51
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Make count-only Vulkan queries easier to read by replacing
nwith descriptive names for queue-family properties, extension properties, and surface formats. Update the comments and build notes to describe the compiler bugs as historical compatibility concerns.All typed-null expressions, array casts, explicit
sizeof(Type)calls, helper functions, compiler pins, and dependency pins remain unchanged. A V scanner comparison against the base branch verifies that executable tokens differ only in the intended local-variable names; manifest files are byte-for-byte identical andgit diff --checkpasses. Existing platform CI will be reviewed before merge.