-
Notifications
You must be signed in to change notification settings - Fork 53
Closed
Labels
asyncAsynchronous operations and callbacksAsynchronous operations and callbackserrorsError reportingError reportinghas resolutionIssue is resolved, just needs to be doneIssue is resolved, just needs to be done
Description
Currently we report DeviceLost in the following places aside from just the DeviceLost callback - places where the JS API does not report it:
- MapAsyncStatus (see WGPUBufferMapAsyncStatus error codes #183)
- CompilationInfoRequestStatus
- CreatePipelineAsyncStatus
- WorkDoneStatus
- PopErrorScope
- GetCurrentTextureStatus (after swapchain & presentation rework #203)
The JS API specifies generally that async operations pretend to work successfully after the device is lost (except for MapAsync): gpuweb/gpuweb#1629 (comment)
Should we keep these DeviceLost enum values or should we do more like what the JS API does and pretend everything worked? Notably WASM can only do what JS does, so this makes it a native-only return value - but so are many of the others.
Metadata
Metadata
Assignees
Labels
asyncAsynchronous operations and callbacksAsynchronous operations and callbackserrorsError reportingError reportinghas resolutionIssue is resolved, just needs to be doneIssue is resolved, just needs to be done