Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2025-06-12T05:33:16+00:00 2025-06-12T05:33:16+00:00 Jay Kwak 82421531+jkwak-work@users.noreply.github.com 2025-06-12T05:33:16+00:00 urn:sha1:7dad68f869502e5c0ab32c12cbf8db866e020713 This PR replaces enable/disable style C function calls with C++ RAII style code. In debug build, when an assertion failed in between enable and disable functions, an exception is thrown and the disable function is not called. RAII style code is safer for an exception 2025-06-04T01:41:26+00:00 Jay Kwak 82421531+jkwak-work@users.noreply.github.com 2025-06-04T01:41:26+00:00 urn:sha1:7f6b683a623ee434e6c720b5bf6c298f389d4b82 2024-02-21T07:13:29+00:00 Yong He yonghe@outlook.com 2024-02-21T07:13:29+00:00 urn:sha1:2e2c7943da89b0100db3bba4b11267b5a857ca92 * Language server robustness fix. * Allow parameter name to be the same as its type. * fix * Fix test. 2021-06-06T16:27:19+00:00 T. Foley tfoleyNV@users.noreply.github.com 2021-06-06T16:27:19+00:00 urn:sha1:688d5fa6eb2c7f5281e50ace1401737479911ebc * Include a "stack trace" with nested-import errors When errors occur in nested `#include` files it is often helpful to have a "stack trace" / traceback of the `#include` chain that led from a root translation unit to the file with an error. This change implements a similar feature for `import`s. It is worth noting that `import`s don't really *require* this kind of compiler support the way `#include`s do because the intention is that the meaning of an `import`ed file does not depend on the order or nesting of `import`s. As such, when trying to *fix* an error in an `import`ed file, you usually don't care how it came to be `import`ed into your shaders. The use case here is somebody adapting a large body of Slang code to use in a different codebase, such that they have certain `.slang` files they don't actually intend to have compile correctly, and they want to be able to diagnose how they came to include those files when/if they cause problems. The actual feature implementation is pretty simple because we already track a stack of active `import`s so that we can detect and diagnose recursive `import`s. This change simply changes the disagnostics when there is an error in imported code so that instead of just noting the inner-most `import` site it lists all the `import` sites that were active at the time. The change includes a test case to confirm that the behavior works (at least for the case of a parse error). * fixup: test outputs Co-authored-by: Yong He <yonghe@outlook.com> Co-authored-by: jsmall-nvidia <jsmall@nvidia.com>