Coroutines in Whidbey?
So what is Scoble censoring here?
Interesting. All the yields at the top lead my guess towards coroutines, but who knows [1]. Hopefully it's something cool that we don't already know about (like generics or partial types, etc.). The very idea that there are undisclosed new features for C# is tres cool.
Anders is coolest thing in the picture anyway, but I'm a card carrying groupie.
[1] This is probably just because I was reading Ajai Shankars .NET Coroutines article in MSDN mag the other night (so now, tristero-like, everywhere I look I see coroutines).
Update: In Scoble's comments, Tim Sneath indicated that what Scoble's obscuring is already announced and EricGu also commented that it's just iterators and some new syntax that he says won't be public until PDC.
I'd read parts of the whitepaperTim Sneath pointed to previously, and frankly it was hard for me to focus after I got all excited about generics and partial types. Going back through it, iterators are discussed, no anchor so I'll recap.
As it turns out, iterators are going to behave like coroutines:
When we implemented the enumerator pattern, we found that we needed to maintain an internal state machine in order to keep track of where we were in the data structure. Iterators have built-in state machines. Using the new yield keyword, we can return values back to the foreach statement that called the iterator. The next time the foreach statement loops and calls the iterator again, the iterator will begin its execution where the previous yield statement left off.