Ben Clayton

This issue appears to be reproducible with Clang 14, but not with Clang 12 (!?) Update: Clang 13 also works (non-reproducable)

TL;DR: My issues went away after updating to CMake to [`v3.24.1`](https://github.com/Kitware/CMake/releases/tag/v3.24.1). If that still doesn't work, consider setting [`CMAKE_LIBRARY_PATH`](https://cmake.org/cmake/help/latest/variable/CMAKE_LIBRARY_PATH.html) to include the path to X11 in your application's `CMakeLists.txt`. ---...

Hi @akien-mga, Related bug: https://github.com/KhronosGroup/glslang/issues/2283 I'm not entirely sure about versioning the libraries aside from `glslang` - the reason being there's no clearly defined public interface for these libraries. If...

This is something I'm actively looking into for multiple projects. Assigning to myself.

Note, I haven't attempted to compile this, but I think your example can be simplified down to: ```C++ #if SHADERC_ENABLE_WGSL_OUTPUT == 1 auto program = tint::reader::spirv::Parse(std::vector(result.begin(), result.end())); if (!program.IsValid()) {...

> @ben-clayton we build swiftshader Debug because ... I didn't think about it and just inherit the build settings from the outer project. Can we change the subproject to build...

> we can make this an error at createShaderModule time, since it's not useful for either users or implementors I prefer this option.

> The intention is that initializers are limited to creation-time expressions for module-scope variables; however, it appears that restriction was missed when creation-time expressions were introduced. Previously, the grammar enforced...

`64k bytes` does seem small for any array. Wouldn't this error out on most medium to large storage buffers?

Note: When we finally spec the inferred-type array constructor (`array(1,2,3)`), this will also need to apply to arrays.