VB -> C#: Field initializers referencing non-static fields

Input code

Public Class A
    Private x As Integer = 2
    Private y(x) As Integer
End Class

Erroneous output

public class A
{
    private int x = 2;
    private int[] y = new int[x + 1];
}

Expected output

public class A
{
    private int x = 2;
    private int[] y;
    public A()
    {
        y = new int[x + 1];
    }
}

Details

Product in use: VS extension

Version in use: 6.6.0

Accessing a non-static field in C# is an error, where it allowed in VB (CS0236).

It’s a bit more complicated than this, since you need to account for multiple constructors.

[tverweij]

@GrahamTheCoder " I don’t know what the VB order is"

The VB Initializers run within the constructor before any other constructor code in the sequence top to bottom as they are defined in the class.

So the VB code:

Public Class x
    public property a As String =b
    private property b As String = "ABC"

    Public Sub New()
        b = "123"
    End Sub
End Class

translate to c# as:

public class x
{
    public string a { get; set; };
    private string b { get; set; };
    public x()
    {
        //field initializers
        a = b  //so result of a is null and NOT ABC or 123
        b = "ABC"
        //end field initializers
        //rest of the constructor code
        b= "123";
    }
}

[GrahamTheCoder]

I’m consolidating the remainder of #418 here: The reference to a non-static might be inside a lambda, but the initialization it still needs to be moved to the constructor:

Imports System.IO

Public Class Test
    Private lambda As System.Delegate = New ErrorEventHandler(Sub(a, b) Len(0))
    Private nonShared As System.Delegate = New ErrorEventHandler(AddressOf OnError)

    Sub OnError(s As Object, e As ErrorEventArgs)
    End Sub
End Class