Feature/initialize list side branch (#6058)

* 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>

1 files changed, 4 insertions, 1 deletions

diff --git a/tests/language-feature/initializer-lists/inheritance-generic.slang b/tests/language-feature/initializer-lists/inheritance-generic.slang
index c916178b8..d5b923afe 100644
--- a/tests/language-feature/initializer-lists/inheritance-generic.slang
+++ b/tests/language-feature/initializer-lists/inheritance-generic.slang
@@ -19,7 +19,10 @@ RWStructuredBuffer<int> result;
 [numthreads(1, 1, 1)]
 void computeMain()
 {
-    Derived<3> d;
+    // Previously, this test is just test we can handle the base constructor invoke correctly,
+    // so we don't construct the Derived object, since #6058, there will not be implicit constructor
+    // to construct the struct, we will have to invoke the constructor explicitly.
+    Derived<3> d = {1,1,1};
 
     // BUFFER: 1
     result[0] = d.a;