Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 759601
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T15:36:58+00:00 2026-05-14T15:36:58+00:00

How yield implements the pattern of lazy loading ?

  • 0

How yield implements the pattern of lazy loading?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-14T15:36:58+00:00Added an answer on May 14, 2026 at 3:36 pm

    yield implementation doesn’t reach the code until it’s needed.

    For example, this code:

    public IEnumerable<int> GetInts()
    {
        yield return 1;
        yield return 2;
        yield return 3;
    }
    

    Will actually compile into a nested class which implements IEnumerable<int> and the body of GetInts() will return an instance of that class.

    Using reflector you can see:

    public IEnumerable<int> GetInts()
    {
        <GetInts>d__6d d__d = new <GetInts>d__6d(-2);
        d__d.<>4__this = this;
        return d__d;
    }
    

    Edit – adding more info about GetInts implementation:
    The way this implementation makes it lazy is based on the Enumerator MoveNext() method. When the enumerable nested class is generated (<GetInts>d__6d in the example), it has a state and to each state a value is connected (this is a simple case, in more advanced cases the value will be evaluated when the code reach the state). If we take a look in the MoveNext() code of <GetInts>d__6d we’ll see the state:

    private bool MoveNext()
    {
        switch (this.<>1__state)
        {
            case 0:
                this.<>1__state = -1;
                this.<>2__current = 1;
                this.<>1__state = 1;
                return true;
    
            case 1:
                this.<>1__state = -1;
                this.<>2__current = 2;
                this.<>1__state = 2;
                return true;
    
            case 2:
                this.<>1__state = -1;
                this.<>2__current = 3;
                this.<>1__state = 3;
                return true;
    
            case 3:
                this.<>1__state = -1;
                break;
        }
        return false;
    }
    

    When the enumerator is asked for the current object it returns the object which is connected to the current state.

    In order to show that the code is evaluated only when it’s required you can look at this example:

    [TestFixture]
    public class YieldExample
    {
        private int flag = 0;
        public IEnumerable<int> GetInts()
        {
            yield return 1;
            flag = 1;
            yield return 2;
            flag = 2;
            yield return 3;
            flag = 3;
        }
    
        [Test]
        public void Test()
        {
            int expectedFlag = 0;
            foreach (var i in GetInts())
            {
                Assert.That(flag, Is.EqualTo(expectedFlag));
                expectedFlag++;
            }
    
            Assert.That(flag, Is.EqualTo(expectedFlag));
        }
    }
    

    I hope it’s a bit more clear. I recommend to take a look at the code with Reflector and observe the compiled code as you change the “yield” code.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.