Fix ConstructorProvider.Initializer not populated for custom constructors

[Copilot]

The ConstructorProvider.Initializer property was not being populated when parsing custom constructors with initializers (: this(...) or : base(...)). This meant that constructor initializer information was lost during code generation.

Problem

When custom constructors contained initializers like:

public Foo(int bar) : this(bar, "default")
{
}

The ConstructorProvider.Signature.Initializer property would be null instead of containing the initializer information.

Root Cause

The issue was in NamedTypeSymbolProvider.BuildConstructors() method which creates ConstructorSignature objects from Roslyn IMethodSymbol data. The method was not extracting constructor initializer information from the syntax tree, so the Initializer parameter was always defaulting to null.

Solution

• Added ExtractConstructorInitializer method - Analyzes constructor syntax using Roslyn to detect and extract initializer information from ConstructorDeclarationSyntax
• Enhanced BuildConstructors - Now passes the extracted initializer to the ConstructorSignature constructor
• Added expression conversion logic - Handles conversion of constructor arguments to appropriate ValueExpression types for both literals and identifiers
• Comprehensive test coverage - Added tests covering this initializers, base initializers, and constructors without initializers

Testing

Added comprehensive test cases in ConstructorInitializerTests:

• CustomConstructorWithThisInitializerShouldHaveInitializerPopulated - Validates : this(...) initializers
• CustomConstructorWithBaseInitializerShouldHaveInitializerPopulated - Validates : base(...) initializers
• CustomConstructorWithoutInitializerShouldHaveNullInitializer - Ensures constructors without initializers still work correctly

All tests pass, including existing test suites (41 NamedTypeSymbolProvider tests, 2 ConstructorProvider tests).

Fixes #6717.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• aka.ms
  • Triggering command: curl -I -sSL --retry 5 --retry-delay 2 --connect-timeout 15 REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.