Comments on: I love FirstOrDefault

By: Boris Juraga

Boris Juraga — Sat, 12 Nov 2011 15:12:00 +0000

So far i have had 1 trouble with it in .NET CF 3.5

List containing:
aaaaa
aabbb
abbcc
abccc
abcdd

var one = (from p in List where p.StartsWith(“abcd”) select p).FirstOrDefault();

one is null.

How is that possible?

By: Zgraf

Zgraf — Wed, 27 Jul 2011 16:56:00 +0000

Rock on. Thanks for explaining this with a clean, simple C# example.

By: Anonymous

Anonymous — Fri, 10 Jun 2011 05:57:00 +0000

myTable.firstOrDefault

or myTable.Take(1).FirstOrDefault ? for select top 1 * from myTable

By: Amila Rajapakse

Amila Rajapakse — Sun, 22 May 2011 09:45:00 +0000

love C#

By: Code Monkey Labs

Code Monkey Labs — Sun, 28 Sep 2008 03:47:49 +0000

Weekly Web Nuggets #31…

General Commented-Out Code & Broken Windows : Jan Van Ryswyck says what everyone is thinking – commented code introduces a lot of mess into your code. There’s a reason we use version control systems…just delete that code! I Love …

By: J.P. Hamilton

J.P. Hamilton — Wed, 24 Sep 2008 16:59:01 +0000

Learn something new every day. I didn’t know the method could take a lambda…guess I wasnt paying attention. I thought you had to do this:

return list.Where(blah blah).FirstOrDefault();

Nice.

By: Reflective Perspective - Chris Alcock » The Morning Brew #186

Reflective Perspective - Chris Alcock » The Morning Brew #186 — Wed, 24 Sep 2008 06:59:46 +0000

[...] I love FirstOrDefault – Chris Brandsma shows how Linq’s FirstOrDefault extension method can improve your code. [...]

By: Jarod

Jarod — Wed, 24 Sep 2008 00:08:26 +0000

I think its important to point out that FirstOrDefault or SingleOrDefault are extension methods of IEnumerable, and Enumerate when called.

@Jamie

The example above is using List, so your arguments are fair. However, if you where working with IEnumerable, you would be forced to enumerate somehow before your example would work. (such as calling ToList())

In that case, FirstOrDefault does it all in one shot, is is much simpler, and doesnt force you to copy to the whole collection to a list when all you want is one object.

By: Jamie

Jamie — Tue, 23 Sep 2008 21:38:06 +0000

Example 1: return list.Count > 0 ? list[0] : null;

Example 2: return list.Find(“whatever”);
or, if List.Find(T item) did not yet exist, return list.Contains(“whatever”) ? “whatever” : null;

Are not all that worse than the FirstOrDefault code, are they?

By: Jason

Jason — Tue, 23 Sep 2008 21:09:18 +0000

Dang, trasa beat me to my comment. I’ve had one project in particular where SingleOrDefault() caught some false assumptions about a sproc. On the other hand SingleOrDefault() doesn’t return as soon as an item is found (on IEnumerable) so it might be slightly slower on large collections. Not sure about the execution times of the two methods on LTS. I’m curious now, so I might check it out.

My personal favorite Linq extension methods are of the filtering and aggregate types. I use list.Any(item => item.IsSomethingTrue) and list.Max(item => item.Property) a lot.