Don't re-initialize static fields in Console

[marek-safar]

the compiler is not capable removing the initialization

[ghost]

Tagging subscribers to this area: @eiriktsarpalis
Notify danmosemsft if you want to be subscribed.

[stephentoub]

the compiler is not capable removing the initialization

It's fine to remove the = false, but the C# compiler does remove those assignments. It will still generate an empty cctor, though, if those would have been the only initialization; that's tracked by dotnet/roslyn#42985. In this case, at least one other field is initialized, so the static cctor is still required.

[marek-safar]

but the C# compiler does remove those assignments

It does not in all cases like this one. It does remove the assignments only where there is no needed assignment. Simple example bellow

class C
{
    static object o = new object ();
    static bool b = false;
}

[stephentoub]

It does not in all cases like this one.

If that's true that's a bug. Have you opened one on dotnet/roslyn?

[EgorBo]

I see there are more cases like this in BCL (I used static (.*) = null; and static (.*) = false; regex in VSCode)

[marek-safar]

Have you opened one on dotnet/roslyn?

Tracking at dotnet/roslyn#43652 but I don't agree this is a bug.

[marek-safar]

I see there are more cases like this in BCL (I used static (.) = null; and static (.) = false; regex in VSCode)

@EgorBo could you submit PR to clear them up?