-
Notifications
You must be signed in to change notification settings - Fork 45
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
WGPUBufferMapAsyncStatus error codes #183
Comments
|
Actually, MapAsync is a little different from others in that it has two error types in the JS spec, OperationError and AbortError. I think these need to be two different values in the enum. |
We also need to actually pick names, for example:
|
FWIW, most of the other status codes all drop the object name:
The only ones that have the object name prepended (if I didn't miss any) are |
May 23 meeting:
|
Right now we have a bunch of error codes in WGPUBufferMapAsyncStatus for different failures. The pattern used elsewhere looks more like a generic Error enum value + a
const char * message
. Should mapAsync change to that?The text was updated successfully, but these errors were encountered: