#LYNC FOR MAC 14.07 HOW TO#
#LYNC FOR MAC 14.07 UPDATE#

Perhaps you want to create a new IEnumerable from the existing values. items.Aggregate(initial, (acc, x) => ComputeAccumulatedValue(acc, x)) If you are actually just aggregating (accumulating) some value then you should consider the Aggregate extension method.

#LYNC FOR MAC 14.07 HOW TO#

More often than not there is a simple LINQ query waiting to be discovered accompanied by a answer by either Jon Skeet, Eric Lippert, or Marc Gravell explaining how to do what you want! Some examples However in my experience side-effects are usually not required. People aren't surprised when side-effects happen here. I'd like to do the equivalent of the following in LINQ, but I can't figure out how:Īs others have pointed out here and abroad LINQ and IEnumerable methods are expected to be side-effect free.ĭo you really want to 'do something' to each item in the IEnumerable? Then foreach is the best choice. Keep your Side Effects out of my IEnumerable If you have resharper, notice the warning

Var evaluatedObservable = observable.ToEnumerable().Select(func => func()).ToList() Simulate subscribing and evaluating Funcs Var observable = Observable.Create>(source => Yes, I know there is an Observable.Range.

The following test using 'ForEach' extension method passes: If using 'foreach', this could produce very strange and potentially non-deterministic results. Typically the code subscribed to the observable is executed asynchronously and potentially in another thread. Obviously there are better ways to create this observable, I am only attempting to demonstrate a point. I'm only using Observable because it's not entirely far fetched to do something like this. Public static void ForEach(this IEnumerable Action action)įoreach (T item in for the overly contrived example. Take the following examples using the functionally equivalent extension method to that in Kalseth's answer. This is only 'harmful' because of the way 'foreach' is implemented in C#. See all of the questions concerning ' Access to modified closure'Īs well as ' Closing over the loop variable considered harmful'. The problem with 'foreach' in C# prior to 5.0, is that it is inconsistent with how the equivalent 'for comprehension' works in other languages, and with how I would expect it to work (personal opinion stated here only because others have mentioned their opinion regarding readability).

#LYNC FOR MAC 14.07 UPDATE#

Update : Apparently as of C# 5.0, the behavior of foreach described below has been changed and ' the use of a foreach iteration variable in a nested lambda expression no longer produces unexpected results.' This answer does not apply to C# ≥ Skeet and everyone who prefers the foreach keyword.

Lync for mac 14.07