Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2025-02-11T00:42:08+00:00 2025-02-11T00:42:08+00:00 Anders Leino aleino@nvidia.com 2025-02-11T00:42:08+00:00 urn:sha1:3c2d46aa1c8575dc046d7457793e77c7a4789093 * Remove the docs/proposals directory This directory will get added to the spec repository in the following PR: https://github.com/shader-slang/spec/pull/6 This closes #6155. * Remove entry from .github/CODEOWNERS file * Redirect some proposal references --------- Co-authored-by: Yong He <yonghe@outlook.com> 2025-02-06T06:35:36+00:00 Yong He yonghe@outlook.com 2025-02-06T06:35:36+00:00 urn:sha1:6b63ff0265ee9bdb8229bb12c71c223c00de0ffa * Allow tuples to work with initiailizer list. * Update definition of C-Style types. 2025-02-05T18:37:03+00:00 kaizhangNV 149626564+kaizhangNV@users.noreply.github.com 2025-02-05T18:37:03+00:00 urn:sha1:9ec6b91686b651d959fd9ffbec283845bd725dd6 * SP004: implement initialize list translation to ctor - We synthesize a member-wise constructor for each struct follow the rules described in SP004. - Add logic to translate the initialize list to constructor invoke - Add cuda-host decoration for the synthesized constructor - Remove the default constructor when we have a valid member init constructor - Disable -zero-initialize option, will re-implement it in followup (#6109). - Fix the overload lookup issue When creating invoke expression for ctor, we need to call ResolveInvoke() to find us the best candidates, however the existing lookup logic could find us the base constructor for child struct, we should eliminate this case by providing the LookupOptions::IgnoreInheritance to lookup, this requires us to create a subcontext on SemanticsVisitor to indicate that we only want to use this option on looking the constructor. - Do not implicit initialize a struct that doesn't have explicit default constructor. Co-authored-by: slangbot <186143334+slangbot@users.noreply.github.com> 2024-11-29T07:02:19+00:00 Bruce Mitchener bruce.mitchener@gmail.com 2024-11-29T07:02:19+00:00 urn:sha1:c3557978cf0184aaf75c27c309bc87e84fd6ab79 Co-authored-by: Ellie Hermaszewska <ellieh@nvidia.com> 2024-09-27T21:18:49+00:00 Yong He yonghe@outlook.com 2024-09-27T21:18:49+00:00 urn:sha1:23216388d1e2a1baa313a1811974de022c552476 * Design proposal for initialization. * extension * QA * wording * Update design. * more revisions. * revise text. * rewording to be more accurate. * Fix wording and add explanation to examples. * clarify on zero initialization. * refine the rules and examples. * update status.