[dawn][common] Remove TypedInteger consteval overloads See https://dawn-review.googlesource.com/c/dawn/+/310677 (which added the consteval overloads) for an explanation of the problem. With the constEVAL overloads, they can get selected even in non-consteval contexts depending on the argument type. Without them, there's only a constEXPR overload available to select, which is valid anywhere. Note, this requires peppering 'u' suffixes over a ton of code. This is super annoying, but the only alternatives I found were: - Leave as is with the confusing error message. - Have a constEXPR overload for the same thing, that calls DAWN_UNREACHABLE when it's used in a runtime context. This won't catch errors until runtime so would be annoying to iterate in development. Bug: 515794394 Change-Id: Ia71a8891e7729a8ea1ffc506745556f612f93450 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/310678 Reviewed-by: Antonio Maiorano <amaiorano@google.com> Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Dawn is an open-source and cross-platform implementation of the WebGPU standard. More precisely it implements webgpu.h that is a one-to-one mapping with the WebGPU IDL. Dawn is meant to be integrated as part of a larger system and is the underlying implementation of WebGPU in Chromium.
Dawn provides several WebGPU building blocks:
webgpu.h version that Dawn implements.webgpu.h.Helpful links:
Developer documentation:
User documentation: (TODO, figure out what overlaps with the webgpu.h docs)
BSD 3-Clause License, please see LICENSE.
This is not an officially supported Google product.