这是indexloc提供的服务,不要输入任何密码
Skip to content

Portability concern about adapter extensions and limits #684

@kvark

Description

@kvark

The current API model is GPUAdapter exposing limits and extensions, and in GPUDeviceDescriptor the user can opt into higher-than-standard limits by providing these structures.

The use case I'm worried about is people just passing the GPUAdapter capabilities straight into requestDevice regardless of which they need. Why this is concerning: developers tend to use more capable machines. They can easily hit a situation where something that works on their machine suddenly doesn't work on a user machine. This is a portability problem by definition.

Perhaps, if we just make it a little bit less straightforward to request all the limits and extensions (for example, have an API requesting a single limit/extension), then dev wouldn't be encouraged to do the wrong thing here.

(spawned from a Matrix discussion)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions