You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, volk creates function pointers for all Vulkan API and extensions that are defined in the vulkan header. If instead the user could define (I suppose via macro defines) which core version + extension are being used, it would have the following advantages:
Only functions that the user plans to use are actually resolved, speeding up initialization
It prevents the user from accidentally using functions from extensions or core versions that were not declared
The text was updated successfully, but these errors were encountered:
Currently, volk creates function pointers for all Vulkan API and extensions that are defined in the vulkan header. If instead the user could define (I suppose via macro defines) which core version + extension are being used, it would have the following advantages:
The text was updated successfully, but these errors were encountered: