Goglides Dev 🌱

Cover image for What Does Yield Do In C#: A Simplified View For Beginners
Dev Leader
Dev Leader

Posted on • Originally published at devleader.ca

What Does Yield Do In C#: A Simplified View For Beginners

The post What Does yield Do In C#: A Simplified View For Beginners appeared first on Dev Leader.

New to the dotnet world? You may have come across it and wondered what does yield do in C#. At its core, yield is a powerful tool that allows for efficient and effective iteration over large datasets. It can help eliminate the need for creating temporary collections or arrays, saving both memory and time. It can transform methods that return collections into what we call iterators in C#.

Throughout the article, we will take a closer look at the benefits of using yield when programming in C# and explore some of the best practices associated with its implementation. Whether you are a beginner or an experienced programmer, this guide will help you understand the yield keyword and harness its power to write better C# code.

Understanding Yield in C

Yield is a C# keyword that allows developers to create custom iterators for their code. When a yield keyword is encountered in a method or operator, it tells the C# compiler that it needs to generate code to create a custom iterator for that method or operator. This iterator is then able to generate a sequence of values that can be iterated over in a foreach loop or similar construct.

Understanding how yield works is important because it can be used to simplify the code, make it more efficient, and make it easier to understand. Of course, this will largely depend on the context — which is likely that you do not want to wait for an entire result set to be allocated.

To use yield in C#, developers need to have a basic understanding of how it works in dotnet and how it can benefit their code.

Requirements for Yield to Work

In order for yield to work, there are specific requirements that need to be met. These requirements include:

  • The method using yield must return either IEnumerable or IEnumerator.

  • The method using yield cannot have any out or ref parameters.

  • The method using yield must use the yield statement at least once.

  • The method using yield cannot be anonymous or a lambda function.

Failing to meet these requirements can result in errors or unexpected behavior in the code. That’s why it’s important to understand why these requirements exist and how to properly utilize yield in your code.

Benefits of meeting these requirements include more efficient code, cleaner code, and easier debugging of issues that may arise in the software development process.

Benefits of Yield

Using yield in C# can provide significant benefits, especially when working with large datasets. One of the main advantages of yield is that it allows for more efficient memory usage because data is generated on-the-fly instead of all at once. This can lead to better performance and fewer memory issues. Without having to allocate an entire result set into memory and working on data on an as-needed basis, you can get some of these benefits.

Yield can also lead to cleaner code by making it easier to implement iterative functions. It allows developers to create iterators that generate values one at a time, which can make code easier to read and understand. Additionally, using yield in C# can lead to more elegant code and can help developers to more accurately convey their intent. None of this is a guarantee, of course, but it’s another tool in your C# toolbox.

By understanding how yield works and the benefits it can provide, developers can make more informed decisions when it comes to utilizing this powerful C# keyword in their software development projects. In other cases, you may want to materialize collections fully. Check out this video for more information on the comparison between yield in C# and materializing a full dataset!

Getting Started with C# Yield Keyword

Once you understand how yield works and the benefits that it can provide, you may be wondering how to get started using yield in your own C# code. There are a few key things to keep in mind when implementing yield, including knowing when to use yield versus return, and some best practices for writing efficient yield code.

Examples of Yield in C

One common use case for yield in C# is when working with large datasets. For example, imagine you need to process a dataset that contains one million records. If you were to read in all of these records at once, you could quickly run into memory and performance issues.

Using yield, you can instead create an iterator that generates one record at a time, allowing you to process the data more efficiently. Here is an example of how this might look in C#:

public IEnumerable<string> ProcessData(IEnumerable<string> input)
    foreach (var item in input)
        // Perform some processing
        var processedItem = DoSomeProcessing(item);

        // Return the processed item using yield
        yield return processedItem;
Enter fullscreen mode Exit fullscreen mode

You could also write an iterator using the C# yield keyword to fetch data:

public IEnumerable<string> GetData()
    // ... get your sql or other DB reader opened
    using reader ...;

    while (reader.Read())
        var currentItem = GetItemFromReader(reader);

        // Return the fetched item using yield
        yield return currentItem;
Enter fullscreen mode Exit fullscreen mode

Yield vs. Return in C

One important thing to keep in mind when using yield in C# is the difference between yield and the return keyword. While both keywords are used to return values from a method or operator, they function in different ways.

When using the return keyword in the context of collections, all values are returned at once when the function is called. This can lead to memory and performance issues, especially when processing large datasets. Of course, if you had a million records in a database that you queried, you may not want to fully materialize that into memory.

When using yield, values are generated on-demand. This allows for more efficient memory usage and faster processing times when you don’t need all of the data or all of the data all at once.

It’s not that one of these is right and one is wrong… They are different tools that you can use! This video helps explain some different design considerations:

Best Practices for Yield Implementation

When implementing yield in your C# code, there are several best practices that can help ensure that your code is efficient, clean, and easy to read. Some of these best practices include:

  • Use the IEnumerable interface when possible, as it is more flexible than IEnumerator.

  • Avoid using the yield keyword in nested loops, as this can lead to performance issues.

  • Use descriptive names for your yield methods and variables.

  • Always include a try-catch block to handle any exceptions that may occur during processing.

  • Keep your yield methods small and focused, and avoid including extraneous logic.

Following these best practices can help you write efficient, effective C# code using the yield keyword. By taking the time to understand how yield works and implementing it correctly in your code, you can significantly improve the efficiency and readability of your C# projects.

Common Mistakes to Avoid With C# yield Keyword

While yield in C# can be awesome for creating iterators, there are some common mistakes that developers should be aware of when working with this keyword. Some common mistakes include:

  • Not properly disposing of the enumerator when processing data.

  • Using too many nested loops, which can lead to performance issues.

  • Using yield in places where it isn’t really needed, which can result in unnecessary complexity.

  • Creating long-running streams or iterators, which can cause memory issues if not properly managed.

To avoid these issues, developers should take care to properly implement yield in their code and follow best practices for using this keyword. It’s also important to thoroughly test code that uses yield to ensure that it operates as expected and doesn’t cause any memory or performance issues.

Something else to consider is over-usage of LINQ, which is built around yield / iterators, can lead to less performant code in some situations. Iterators leveraging the yield keyword CAN be powerful, but iterators can also cause some headaches. Because you’ll get lazy-evaluation with iterators backed by the yield keyword, accidentally re-evaluating them can be expensive.

By avoiding these common pitfalls, developers can make the most of yield in their C# code and take advantage of its benefits for their software projects.

Answering What Does yield Do in C

To recap, yield is a powerful tool for C# developers that may help achieve better performance when working with data sets in C#. This article aimed to provide a guide on how to use yield effectively. I started things off with understanding yield in C#, the benefits of using it, how to implement it, and even some common mistakes.

One of the key takeaways is that yield allows developers to work with large datasets efficiently. By using yield, you can make the most of the resources available to you and provide better results to users. When you don’t need all of the data at once, this can be helpful!

Overall, yield can be a useful feature for C# developers to understand and apply effectively. As a software engineer, you should take the time to learn how to use yield in your projects to achieve the best possible results! If you’re interested in more learning opportunities, subscribe to my free weekly newsletter and check out my YouTube channel!

Want More Dev Leader Content?

  • Follow along on this platform if you haven’t already!

  • Subscribe to my free weekly software engineering and dotnet-focused newsletter. I include exclusive articles and early access to videos:


  • Looking for courses? Check out my offerings:


  • E-Books & other resources:


  • Watch hundreds of full-length videos on my YouTube channel:


  • Visit my website for hundreds of articles on various software engineering topics (including code snippets):


  • Check out the repository with many code examples from my articles and videos on GitHub:


Top comments (0)