Introduction Side-effects don’t fit together very well with functional-style delayed computation, as observed in LINQ. Having such constructs embedded in an otherwise eagerly evaluated imperative language like C# can cause quite some confusion from time to time. A few samples (due to Erik Meijer) of such “mishaps” are shown below: // // When does it throw? // IEnumerable res = null; try { res = from x in Enumerable.
read more
Modifying Windows Store Grid App – IEnumerable, Data Binding, LINQ Queries Read Post
The‘GroupBy’ feature in LINQ is amazing and very powerful. When you use a‘GroupBy’ in LINQ, internally it calls an extension method whichreturns a sequence of System.Collections.Generic.IEnumerable)>)>)>)TheGroupBy... Read Post
Introduction Declarative language constructs like query comprehension syntax often worries imperatively trained developers. I hear this quite a bit, and the excuse of “It Just Works” is often not satisfactory for most of them :-). C... Read Post