25. October 2008 06:32
C# 2.0 introduced the "yield return" statement. While neat in theory, I actually never ran into a scenario where I needed it. I had heard all the rage about it, but to me, it was kinda like the 5th wheel on the cart of awesomeness that was C# 2.0. My opinion changed this morning when I needed a simple way to depth-first iterate over the items in a tree.
My original solution was to use a stack, build up a collection of the nodes in the tree, then return the collection, but that actually didn't work too well in my case (I was doing something screwy with the collection later on that was making ActiveRecord angry). It also wasted memory. Yeah, memory is cheap, but why waste it?
After thinking on it for a little bit, I decided I'd implement a custom IEnumerator for my tree, but then I remembered that I could just use 'yield return'. 5 lines of code later, we have it:
1: public IEnumerator<TreeNode> GetDepthFirstEnumerator()
3: yield return this;
5: foreach (TreeNode child in ChildNodes)
7: IEnumerator<TreeNode> childEnumerator = child.GetDepthFirstEnumerator();
9: while (childEnumerator.MoveNext())
11: yield return childEnumerator.Current;
Surprisingly, this works fine even with recursion!
About Matt Honeycutt...
Matt Honeycutt is a software architect specializing in ASP.NET web applications, particularly ASP.NET MVC. He has over a decade of experience in building (and testing!) web applications.
He’s an avid practitioner of Test-Driven Development, creating both the SpecsFor and SpecsFor.Mvc frameworks.
He's also an author for Pluralsight,
where he publishes courses on everything from web applications to testing!