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

  • SEARCH
  • Home
  • 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 989551
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T05:48:40+00:00 2026-05-16T05:48:40+00:00

What is the concrete type for this IEnumerable<string> ? private IEnumerable<string> GetIEnumerable() { yield

  • 0

What is the concrete type for this IEnumerable<string>?

private IEnumerable<string> GetIEnumerable()
{
    yield return "a";
    yield return "a";
    yield return "a";
}
  • 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-16T05:48:41+00:00Added an answer on May 16, 2026 at 5:48 am

    It’s a compiler-generated type. The compiler generates an IEnumerator<string> implementation that returns three “a” values and an IEnumerable<string> skeleton class that provides one of these in its GetEnumerator method.

    The generated code looks something like this*:

    // No idea what the naming convention for the generated class is --
    // this is really just a shot in the dark.
    class GetIEnumerable_Enumerator : IEnumerator<string>
    {
        int _state;
        string _current;
    
        public bool MoveNext()
        {
            switch (_state++)
            {
                case 0:
                    _current = "a";
                    break;
                case 1:
                    _current = "a";
                    break;
                case 2:
                    _current = "a";
                    break;
                default:
                    return false;
            }
    
            return true;
        }
    
        public string Current
        {
            get { return _current; }
        }
    
        object IEnumerator.Current
        {
            get { return Current; }
        }
    
        void IEnumerator.Reset()
        {
            // not sure about this one -- never really tried it...
            // I'll just guess
            _state = 0;
            _current = null;
        }
    }
    
    class GetIEnumerable_Enumerable : IEnumerable<string>
    {
        public IEnumerator<string> GetEnumerator()
        {
            return new GetIEnumerable_Enumerator();
        }
    
        IEnumerator IEnumerable.GetEnumerator()
        {
            return GetEnumerator();
        }
    }
    

    Or maybe, as SLaks says in his answer, the two implementations end up in the same class. I wrote this based on my choppy memory of generated code I’d looked at before; really, one class would suffice, as there’s no reason the above functionality requires two.

    In fact, come to think of it, the two implementations really should fall within a single class, as I just remembered the functions that use yield statements must have a return type of either IEnumerable<T> or IEnumerator<T>.

    Anyway, I’ll let you perform the code corrections to what I posted mentally.

    *This is purely for illustration purposes; I make no claim as to its real accuracy. It’s only to demonstrate in a general way how the compiler does what it does, based on the evidence I’ve seen in my own investigations.

    • 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.