LINQ Farm: LINQ Sets

DotNetKicks.com — Fri, 29 Dec 2006 09:11:57 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com

re: LINQ Farm: LINQ Sets

zproxy — Fri, 29 Dec 2006 09:56:42 GMT

Why o why are you using

where p.OperatorType.Equals(operatorType)

In case of comparing string to string the == operator is sufficient.

where p.OperatorType == operatorType

cheers.

re: LINQ Farm: LINQ Sets

Charlie Calvert — Sat, 30 Dec 2006 02:20:03 GMT

zproxy,

I asked around, and it looks like you are right. I should have written == instead of calling MyString.Equals. As far as I can tell, the result will be the same in every case unless MyString is null in which case == will handle it correctly and MyString.Equals will blow up.

Here is some code I played around with once you got me interested in this subject:

string a = "foo";

string b = "foo";

string c = string.Copy(a);

string d = null;

Console.WriteLine(a == b);

Console.WriteLine(a == c);

Console.WriteLine(a.Equals(b));

Console.WriteLine(a.Equals(c));

Console.WriteLine(String.Equals(a, b));

Console.WriteLine(String.Equals(a, c));

Console.WriteLine(String.Equals((object)a, (object)b));

Console.WriteLine(String.Equals((object)a, (object)c));

Console.WriteLine((object)a == (object)c);

Console.WriteLine(String.ReferenceEquals(a, b));

Console.WriteLine(String.ReferenceEquals(a, c));

Console.WriteLine(d == a);

Console.WriteLine(d.Equals(a));

- Charlie

re: LINQ Farm: LINQ Sets

scobrown — Tue, 13 Mar 2007 19:25:25 GMT

How does the performance compare between a set function like Except and a Where function?

Suppose you needed both a list of even numbers and a list of odd numbers. Would you be better off deriving both from the original list using Where? Or deriving one and using Except to generate the other?

Would it matter how many items were in the list?

LINQ Farm: More on Set Operators

Charlie Calvert's Community Blog — Sun, 13 Jul 2008 19:38:23 GMT

This is a second article on the LINQ Set operators, the first being published while LINQ was still in