C# LINQ

An explicit loop explains how to visit items, test them, and append matches. LINQ lets code describe the same transformation through named operations. Where means keep items satisfying a predicate; Select means produce a new value from each item.

LINQ does not replace the need to understand loops. Sequence operators still enumerate data, call delegates, allocate results when materialized, and may perform substantial work. The higher-level vocabulary helps when it makes the transformation easier to verify.

List<int> numbers = new List<int> { 1, 2, 3, 4, 5 };

IEnumerable<int> squaresOfEvenNumbers = numbers
  .Where(number => number % 2 == 0)
  .Select(number => number * number);

Console.WriteLine(string.Join(", ", squaresOfEvenNumbers));

4, 16

Where keeps or removes original elements. Select changes the shape by mapping each element to another value. OrderBy and ThenBy define ordering. Count, Any, All, Sum, Average, Min, and Max answer aggregate questions. Keeping each step honest makes a pipeline readable from left to right.

Use Any(predicate) to ask whether at least one match exists rather than Count(predicate) > 0. Use FirstOrDefault only when a default or absence has a defined meaning; otherwise a missing result may hide a broken assumption.

Where and Select usually return a description of work rather than executing immediately. Enumeration—foreach, ToList, Count, and similar terminal use—runs the query. This deferred execution lets pipelines compose and observe current source contents, but it can surprise you when the source changes or an expensive query is enumerated twice.

ToList and ToArray materialize a snapshot now. Materialize when you need stable results, repeated enumeration would be costly, or a later layer should receive a concrete collection. Do not call ToList between every operator; it creates unnecessary intermediate collections.

List<int> numbers = new List<int> { 1, 2, 3 };
IEnumerable<int> positives = numbers.Where(number => number > 0);

numbers.Add(4);

Console.WriteLine(string.Join(", ", positives)); // includes 4

A report often needs a different shape from the domain objects. Select can project orders into display strings or dedicated report records without adding presentation-only properties to Order. GroupBy can organize elements by category, but nested group pipelines become harder to debug; name intermediate queries when that improves clarity.

Database-backed LINQ providers may translate expression trees into SQL rather than run ordinary in-memory methods. Not every C# operation can be translated, and performance depends on the generated query. The pipeline vocabulary transfers, but inspect provider documentation and generated queries in real data applications.