-
Notifications
You must be signed in to change notification settings - Fork 61
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
Move destroyInstance to Base level #167
Comments
Yes this annoying, but it does make sense: the instance destructor is specific to one type of instance, so it's depended on the load. To be clear, this is a Vulkan thing and not something that I can really change. If you want to deal with it, you can catch and use a dedicated wrapper that only had the destroy function. If that also fails youre out of luck i guess. Personally i suggest to leak it: the OS will clean things up for you anyway. |
I was mistaken. Perhaps we can add a load function without errors to avoid this situation. |
There's a loadNoFail i think |
If use loadNoFil, how do we check a function valid? Sometimes, the diver is strange, a extension is valid, but related function is invalid, so I must check the function is valid manually. |
Suggestion move destroyInstance to Base level, move destroyDevice to Instance level
destroyDevice is the same
The text was updated successfully, but these errors were encountered: