<feed xmlns='http://www.w3.org/2005/Atom'>
<title>slang.git/tests/compute/extension-on-interface.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>2018-01-16T18:52:10+00:00</updated>
<entry>
<title>Allow extension on interface (#369)</title>
<updated>2018-01-16T18:52:10+00:00</updated>
<author>
<name>Yong He</name>
<email>yonghe@outlook.com</email>
</author>
<published>2018-01-16T18:52:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.yummers.dev/slang.git/commit/?id=59691aeeb013c5bb7cdaa31a6fc572eebd8be610'/>
<id>urn:sha1:59691aeeb013c5bb7cdaa31a6fc572eebd8be610</id>
<content type='text'>
This completes item 5 in issue #361.

The interesting change is that when checking for interface conformance, we include the requirements (include transitive interfaces) defined in extensions as well. (check.cpp line 1946)

All the other changes are for one thing: reoder the semantic checkings to two explicit stages: check header and check body. In check header phase, we check everything except function bodies, register all extensions with their target decls, then check interface conformances for all concrete types. In body checking phase, we look inside the function bodies and check concrete statements/expressions. This change ensures that we take extension into consideration in all places where it should be.</content>
</entry>
</feed>
