Setting multiple indexed objects' property directly via Linq fails

[TylerBrinkley]

Consider the following unit tests. I expect the first test to pass but it doesn't so I must use the second's syntax in order for it to pass. Is there some technical limitation that prevents us from using the first test's syntax or can this be fixed in an update?

public class GivenAnIndexer
{
    [Fact]
    public void WhenQueryingWithTwoIndexes_ThenSetsThemDirectly1()
    {
        var foo = Mock.Of<IFoo>(x => x[0].Value == "hello" && x[1].Value == "goodbye");

        Assert.Equal("hello", foo[0].Value); // Fails here as foo[0] is the same object as foo[1] and foo[1].Value == "goodbye"
        Assert.Equal("goodbye", foo[1].Value);
    }

    [Fact]
    public void WhenQueryingWithTwoIndexes_ThenSetsThemDirectly2()
    {
        var foo = Mock.Of<IFoo>(x => x[0] == Mock.Of<IBar>(b => b.Value == "hello") && x[1] == Mock.Of<IBar>(b => b.Value == "goodbye"));

        Assert.Equal("hello", foo[0].Value); // These pass no problem
        Assert.Equal("goodbye", foo[1].Value);
    }

    public interface IFoo
    {
        IBar this[int index] { get; }
    }

    public interface IBar
    {
        string Value { get; }
    }
}

[kzu]

Sounds like a useful improvement

…

-- /kzu from mobile

[stakx]

Closing this dormant issue, but marking it as "unresolved" so it can be easily found again. Please see #642 for details. If you'd like to pick this up and work on it, please post here briefly and we'll see what we can do!

[stakx]

@TylerBrinkley, in case you're still tracking this, it has been fixed back in Moq 4.11.0.

P.S.: Added your tests to the regression test suite.

[TylerBrinkley]

@stakx That's great news. Thanks!