<feed xmlns='http://www.w3.org/2005/Atom'>
<title>slang.git/tests/diagnostics/uninitialized-resource-type.slang.1.expected, 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>2025-02-12T21:37:05+00:00</updated>
<entry>
<title>Fix crash when handling uninitialized resource type (#6338)</title>
<updated>2025-02-12T21:37:05+00:00</updated>
<author>
<name>kaizhangNV</name>
<email>149626564+kaizhangNV@users.noreply.github.com</email>
</author>
<published>2025-02-12T21:37:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=3f102afe1038882f336dc052a9954811150fa700'/>
<id>urn:sha1:3f102afe1038882f336dc052a9954811150fa700</id>
<content type='text'>
* Fix crash when handling uninitialized resource type

close #6328.

When declare a var with struct type, if the struct has a resource
type field and it doesn't provide explicit constructor, because
slang won't implicit construct such variable at declare site if user
doesn't explicitly call the initializer list, we should report the
resource type field uninitialized as an error to prevent future possible
crash when legalize any use of such variable.</content>
</entry>
</feed>
