Ellie Hermaszewska

For example: - Building slang as part of a higher-level cmake project - Downloading and testing releases - Using slang as a submodule

For https://github.com/shader-slang/slang/pull/4629 Workaround works, but would be a little neater to not do the repacking. Maybe just easier to unpack and sign whatever cpack's made?

we probably don't need the tag for CI and releases should be made from the tagged revision itself we definitely don't need deep checkout for submodules.

at the moment we only test the Ninja generator

Test varying inputs and outputs for wgsl

2

Closes https://github.com/shader-slang/slang/issues/5067 New tests, covering what's declared supported in the WGSL support docs - tests/wgsl/semantic-coverage.slang - tests/wgsl/semantic-depth.slang - tests/wgsl/semantic-dispatch-thread-id.slang - tests/wgsl/semantic-group-id.slang - tests/wgsl/semantic-group-index.slang - tests/wgsl/semantic-group-thread-id.slang - tests/wgsl/semantic-instance-id.slang - tests/wgsl/semantic-is-front-face.slang -...

Closes https://github.com/shader-slang/slang/issues/5562

Closes https://github.com/shader-slang/slang/issues/5263

Following on from this: https://github.com/shader-slang/slang/issues/5660 If we make `I` a generic interface then we get a very bad error message `nullType.slang`: ```slang import nullTypeModule; struct S { } extension S...