Skip to content

WGPUBufferMapAsyncStatus error codes #183

@kainino0x

Description

@kainino0x

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    errorsError reportinghas resolutionIssue is resolved, just needs to be done

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions