Here is an interesting issue I noticed when using the Except Operator: I have list of users from which I want to exclude some users:
The list of users is coming from an XML file:
The code goes like this:
interface IUser { int ID { get; set; } string Name { get; set; } } class User: IUser { #region IUser Members public int ID { get; set; } public string Name { get; set; } #endregion public override string ToString() { return ID + ':' +Name; } public static IEnumerable<IUser> GetMatchingUsers(IEnumerable<IUser> users) { IEnumerable<IUser> localList = new List<User> { new User{ ID=4, Name='James'}, new User{ ID=5, Name='Tom'} }.OfType<IUser>(); var matches = from u in users join lu in localList on u.ID equals lu.ID select u; return matches; } } class Program { static void Main(string[] args) { XDocument doc = XDocument.Load('Users.xml'); IEnumerable<IUser> users = doc.Element('Users').Elements('User').Select (u => new User { ID = (int)u.Attribute('id'), Name = (string)u.Attribute('name') } ).OfType<IUser>(); //still a query, objects have not been materialized var matches = User.GetMatchingUsers(users); var excludes = users.Except(matches); // excludes should contain 6 users but here it contains 8 users } }
When I call User.GetMatchingUsers(users) I get 2 matches as expected. The issue is that when I call users.Except(matches) The matching users are not being excluded at all! I am expecting 6 users ut ‘excludes’ contains all 8 users instead.
Since all I’m doing in GetMatchingUsers(IEnumerable<IUser> users) is taking the IEnumerable<IUser> and just returning the IUsers whose ID’s match( 2 IUsers in this case), my understanding is that by default Except will use reference equality for comparing the objects to be excluded. Is this not how Except behaves?
What is even more interesting is that if I materialize the objects using .ToList() and then get the matching users, and call Except, everything works as expected!
Like so:
IEnumerable<IUser> users = doc.Element('Users').Elements('User').Select (u => new User { ID = (int)u.Attribute('id'), Name = (string)u.Attribute('name') } ).OfType<IUser>().ToList(); //explicity materializing all objects by calling ToList() var matches = User.GetMatchingUsers(users); var excludes = users.Except(matches); // excludes now contains 6 users as expected
I don’t see why I should need to materialize objects for calling Except given that its defined on IEnumerable<T>?
Any suggesstions / insights would be much appreciated.
I think I know why this fails to work as expected. Because the initial user list is a LINQ expression, it is re-evaluated each time it is iterated (once when used in
GetMatchingUsersand again when doing theExceptoperation) and so, new user objects are created. This would lead to different references and so no matches. UsingToListfixes this because it iterates the LINQ query once only and so the references are fixed.I’ve been able to reproduce the problem you have and having investigated the code, this seems like a very plausible explanation. I haven’t proved it yet, though.
Update
I just ran the test but outputting the
userscollection before the call toGetMatchingUsers, in that call, and after it. Each time the hash code for the object was output and they do indeed have different values each time indicating new objects, as I suspected.Here is the output for each of the calls:
And, here is the modified code to show the problem: