KhronosGroup / KhronosGroup/Vulkan-ValidationLayers
Best Practices Layer tracking of used features/extensions
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1k
- Forks
- 505
- Avg merge
- 11h 25m
- Merged PRs (30d)
- 229
Description
Modify the best practices layer to track what extensions and features are enabled but not used by the time vkDestroyDevice and vkDestroyInstance are called. This could help the applications more narrowly request only the features they intend to use and for external applications like GFXReconstruct and RenderDoc to be more prepared for what is actually used by an application were they to follow the best practices request.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the best practices layer handling for vkDestroyDevice and vkDestroyInstance, then trace how enabled extensions and features are recorded. Define how the layer will determine whether each enabled item was used before destruction. Done means the layer reports enabled-but-unused extensions and features at both destruction points, with coverage for the requested behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100