VB -> C#: Namespaces with different cases merged

[mrmonday]

Input code

Namespace [Aaa]
    Friend Class A
    End Class
End Namespace

Namespace Global.aaa
    Friend Class B
    End Class
End Namespace

Friend Module C
    Sub Main()
        Dim x = New aaa.A
        Dim y = New Aaa.B
    End Sub
End Module

Erroneous output

namespace Aaa
{
    internal class A
    {
    }
}

namespace Aaa
{
    internal class B
    {
    }
}

internal static class C
{
    public static void Main()
    {
        var x = new Aaa.A();
        var y = new Aaa.B();
    }
}

Expected output

namespace Aaa
{
    internal class A
    {
    }
}

namespace aaa
{
    internal class B
    {
    }
}

internal static class C
{
    public static void Main()
    {
        var x = new Aaa.A();
        var y = new aaa.B();
    }
}

Details

• Version in use: 7.3.0

The original VB is hard to enter in VS, since it likes to auto-correct. The original case was cross-project, where it's easier to achieve (but harder to put into a test case). According to ILSpy this does end up as two different namespaces.

[GrahamTheCoder]

I've tagged this as compilation error since I believe it's a source (and binary) level break for C# referencing the converted assembly.