Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Menu Close

Laziness in LINQ Select

One of the principles of LINQ is to be lazy. A LINQ query won’t do any work unless you force the query to do the work. Even when a query does perform work – it does the least amount of work possible. Consider the following code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
int checkCount = 0;
// IEnumerable<Guid> groupIdsToCheckMembership
var groupIdsToCheckMembershipString = groupIdsToCheckMembership.Select(x =>
{
    checkCount = checkCount + 1;
    return x.ToString();
});
 
if (checkCount == 0)
{
    TraceLogger.LogInformation(this.context, "No Groups in query.");
    return new List<Guid>();
}
// continue when there are group membership

This code will alawys return new List() and the checkCount will always = 0. Why? Select or Enumerable.Select is defined as “Projects each element of a sequence into a new form by incorporating the element’s index”. Projection is on top of enumerator. For this reason, checkCount = checkCount + 1 was not executed since the array was not enumerating. Once we see the issue, it becomes easy to fix above code. We need to either rewrite Select as loop, or simply force the enumerator to run. For example:

1
2
3
4
5
var groupIdsToCheckMembershipString = groupIdsToCheckMembership.Select(x =>
{
    checkCount = checkCount + 1;
    return x.ToString();
}).ToList();

ToList() converts the IEnumerable to a List object. This forces the enumartor to run along with its projection methods.

Leave a Reply

Your email address will not be published. Required fields are marked *