<feed xmlns='http://www.w3.org/2005/Atom'>
<title>slang.git/tests/bugs/glsl-static-const-array.slang.expected.txt, branch master</title>
<subtitle>Making it easier to work with shaders</subtitle>
<id>https://git.yummers.dev/slang.git/atom?h=master</id>
<link rel='self' href='https://git.yummers.dev/slang.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/'/>
<updated>2019-07-29T21:55:04+00:00</updated>
<entry>
<title>Fix issue with outputting "static" in GLSL (#1006)</title>
<updated>2019-07-29T21:55:04+00:00</updated>
<author>
<name>Tim Foley</name>
<email>tfoleyNV@users.noreply.github.com</email>
</author>
<published>2019-07-29T21:55:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=89758544c45a15e546a1eb08891e2787bb88de4a'/>
<id>urn:sha1:89758544c45a15e546a1eb08891e2787bb88de4a</id>
<content type='text'>
This appears to be a regression introduced in #1001, and missed because none of our existing tests covered `static const` arrays on the GLSL/SPIR-V targets.

The basic problem is that we cannot output a `static const` definition in GLSL because `static` is a reserved word and not a keyword. Instead for GLSL we just want a `const` array. This change makes the emission of `static` for global-scope constants key on the target language for code generation, and only emit it for HLSL, C, and C++.

This change also adds a test case specifically for running Slang input that has a `static const` array on the Vulkan target.</content>
</entry>
</feed>
