Simplify WGPUWaitStatus "Unsupported" cases #499
Merged
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.
Mentioned
WGPUWaitStatus
in #401 but I didn't think about simplifying it so we didn't discuss it.Since we're relying now on "implementation-defined logging" to convey details we don't generally need detailed error codes for things that are just surface-level misuses of the API.
In
WGPUWaitStatus
we have threeUnsupported
cases:WGPUWaitStatus_UnsupportedTimeout
WGPUWaitStatus_UnsupportedCount
WGPUWaitStatus_UnsupportedMixedSources
I don't think these are cases that a program would actually respond to programmatically. So I'm proposing we simplify into just one
WGPUWaitStatus_Unsupported
orWGPUWaitStatus_Error
, with implementation-defined logging.I used
WGPUWaitStatus_Error
here.