Skip to content

[WGSL] WGSL needs a plan for expansion #600

Description

@dneto0

I expect WGSL will evolve over time to incorporate new functionality.

We should make a plan to accommodate that growth.

For example:

  • Account for potential conflict between keywords introduced in a future version of WGSL, vs. identifiers used in today's shaders. Maybe use namespace mechanism?
  • Account for new data types, e.g. IEEE 16bit float, potentially other exotic floating points type like bfloat16. This can impact type derivation / typechecking.
  • Will we require shaders to declare their own version or extensions? This is one approach to accommodating the keyword-conflict issue. GLSL chose this path.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    wgslWebGPU Shading Language Issues

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions