Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2025-07-30T05:51:37+00:00 2025-07-30T05:51:37+00:00 Yong He yonghe@outlook.com 2025-07-30T05:51:37+00:00 urn:sha1:42dc521f7817328a20e40b3352ae667dfd124edb 2025-07-11T21:57:38+00:00 aidanfnv aidanf@nvidia.com 2025-07-11T21:57:38+00:00 urn:sha1:39f3c6c7701ed9d7edd5bfd8ee0adf99d2d658e0 * Use stdout for --help text instead of stderr * format code (#13) Co-authored-by: slangbot <186143334+slangbot@users.noreply.github.com> --------- Co-authored-by: slangbot <ellieh+slangbot@nvidia.com> Co-authored-by: slangbot <186143334+slangbot@users.noreply.github.com> 2025-05-15T22:28:05+00:00 aidanfnv aidanf@nvidia.com 2025-05-15T22:28:05+00:00 urn:sha1:fba75a6f3f3c26b05cf4c826bff4a102972d348c This change uses a different path for accessing the slangc binary during the command line reference doc regeneration action, as the environment variable referenced for the bin directory may not be accurate. This change also makes some exclusions from the slang build in the command line reference actions, to speed up those builds for checking/regenerating. 2025-05-14T16:41:59+00:00 aidanfnv aidanf@nvidia.com 2025-05-14T16:41:59+00:00 urn:sha1:39c9e25f6d728e970b68a9452330e754991b4ac5 This change modifies the code that generates the Command Line Reference doc to output H2 headings in place of H1 headings, and H3 in place of existing H2, so that readthedocs will not treat the additional H1 headings as titles. This change also regenerates the Command Line Reference doc, as the current copy in the repo appears to be quite out-of-date. The existing copy is also encoded as UTF-16LE, whereas the other docs are all UTF-8. The regenerated doc is also UTF-8, and all I did to generate that was run slangc.exe -help-style markdown -h > docs\command-line-slangc-reference.md 2>&1 after building slangc on Windows. This change also adds GitHub actions workflows to check the contents of the doc, fail if a regenerated version needs to be checked in, and provide an option to regenerate it with a bot, all in a similar manner to User Guide TOC regeneration. The doc writer was producing different results from my local build until I changed how the writer sorts the shader stages. In the action, the order of pixel and fragment was reversed, despite the only difference from my local build being the OS. --------- Co-authored-by: slangbot <ellieh+slangbot@nvidia.com> Co-authored-by: slangbot <186143334+slangbot@users.noreply.github.com>