Moq does not distinguish between distinct events if they have the same name

[stakx]

Code to reproduce:

[Fact]
public void Moq_can_distinguish_between_two_events_having_same_name()
{
    var ab = new Mock<object>();
    var a = ab.As<IA>();
    var b = ab.As<IB>();

    var aeRaiseCount = 0;
    (a.Object).E += () => aeRaiseCount++;

    var beRaiseCount = 0;
    (b.Object).E += () => beRaiseCount++;

    a.Raise(m => m.E += null);
    Assert.Equal(1, aeRaiseCount);
    Assert.Equal(0, beRaiseCount);

    b.Raise(m => m.E += null);
    Assert.Equal(1, aeRaiseCount);
    Assert.Equal(1, beRaiseCount);
}

public interface IA
{
    event Action E;
}

public interface IB
{
    event Action E;
}

public class AB : IA, IB
{
    private Action ae;
    private Action be;

    event Action IA.E
    {
        add => this.ae = (Action)Delegate.Combine(this.ae, value);
        remove => this.ae = (Action)Delegate.Combine(this.ae, value);
    }

    event Action IB.E
    {
        add => this.be = (Action)Delegate.Combine(this.be, value);
        remove => this.be = (Action)Delegate.Combine(this.be, value);
    }

    public void RaiseAE() => this.ae?.Invoke();

    public void RaiseBE() => this.be?.Invoke();
}

Expected outcome:

The above test should pass, since IA.E and IB.E implemented by AB are two distinct events.

Actual outcome:

The test fails because Moq treats both events as one and the same.

Additional details:

This is a direct consequence of Moq identifying events by name only, see e.g.:

https://github.com/moq/moq4/blob/0307f25564e75d68f0fc189f4d8c8c800b59f98e/src/Moq/Interception/InterceptionAspects.cs#L209-L263

EventHandlerCollection likewise uses event names as its keys. Using EventInfo would be more correct, but care would have to be taken to properly deal with polymorphism.