This is just one reason why we need interface inheritance

gistfile1.cs

IList<string> list = new [] { "I", "declare", "you", "are", "mistaken", "sir" };
IEnumerable<string> youProposeIShouldNotBeAbleToDoThis = list;
// For the above code to work, IList<T> must inherit from IEnumerable<T>, i.e. interface inheritance must exist.

so what caused the issue today was something like this... granted it might consider "bad code".

public interface IThingRepository : IRepository
{
Thing GetSomeSpecialThing(IQueryObject);
}

implementation : (BaseRepository implements IRepository)

public class ThingRepository: BaseRepository, IThingRepository
{
.....
}
so some code that uses IThingRepository needs to have the save method from IRepository mocked ... so yeah we have a problem...

@skoon that's what we ran into right?? I think I remember it correctly....

So really you're for Interface segregation. I agree. In this case it seems like Command/Query separation. Happens a lot.

I think I would understand better if you present A) this is how it was B) this is how it should be

Yeah that's pretty much it.