ArielG-NV

updated 👍 (also changed the example numbers to make more sense)

I have a question about when an initializer-list is a partial-completion to the public/internal member list: ``` struct S { private int m1 = 0; public int m2; private int...

> As soon as I put private: keyword, the list-initializer didn't work; probably I need to explicitly declare a constructor with a list-initializer as a parameter in this case. This...

Additional planning (generally not C++ aligned behavior): 1. Inheritance ``` //// // module1.slang //// struct MyStructBase { private int v1; public int v2; internal int v3; }; struct MyStruct1 :...

UPDATED - 8/12 Note: ctor is an alias for constructor. We will implement the ctor to adapt for a init-list like so: ``` struct S1 { public int val1; }...

Additional planning: Syntax for constructor: 1. Only a struct that is made by a 'synthesized-ctor' and is a 'base type' may be treated as if its not a separate object...

Breaking change: If a base type struct has no members we no longer require/allow as a parameter into a initializer list the base-type

Update: Flattened initialization lists for structs are allowed if: 1. user did not define a (non default) ctor 2. Internally Slang only auto-generated 1 (non default) ctor for a user...

Sure. Should be solvable with the capability system.

note: need to add GL_EXT_ray_tracing to the implementation (a 4th raytracing ext)