Re: Comment on OperatorsOverview in morelinq

[more...@googlecode.com]

Comment by tormod.s...@gmail.com:

FirstBy would be confusing as the regular "First()" returns a single item.
DistinctBy is returning the first item, which is also what the
regular "Distinct()" does. If the key selector distinct operation doesn't
produce what you want, you are probably looking for GroupBy().
The existing description of Pipe() doesn't set it apart from Select(). The
difference is that Pipe() does eager evaluation. Select accepts method
group.
To turn single element into sequence, use new[]{item}.

The reason I stumbled in here is that the Zip() method in MoreLinq is in
compiler conflict with regular Zip(). If the argument list is the same,
then find a new name for it.

For more information:
http://code.google.com/p/morelinq/wiki/OperatorsOverview

[more...@googlecode.com]

Comment by jonathan.skeet:

@tormod: The reason for Zip is that it doesn't exist in .NET 3.5. We might
want to have two builds: one for .NET 3.5 and one for .NET 4.

[more...@googlecode.com]

Comment by tormod.s...@gmail.com:

@Jon, thank you for replying. I apologize that the last post was sort of
blunt. I was in a hurry and had just skimmed through the thread. I have a
community using LINQPad and they need to either use Zip or MoreLinq, but
cannot practically use both. Could you possibly place the legacy Zip in a
different namespace? It would be a breaking change, but not a biggie.
You probably don't remember me. I approached you and Mads last NDC about
reactive models and combinatory operators that would be reactive and would
also provide current expression value upon initialization.

[more...@googlecode.com]

Comment by jonathan.skeet:

@tormod: I wouldn't want to put it in a different namespace. It makes more
sense to have two different builds. This is discussed in Issue 60.

And yes, I very well remember you from NDC :)

[more...@googlecode.com]

Comment by tormod.s...@gmail.com:

Thinking about it, one should probably prepare for more of MoreLinqs'
operators being provided out of the box with LINQ in the future.
Also, MoreLinq will probably provide backporting of upcoming LINQ operators.

In that respect, different builds may make more sense for the consumer.

[more...@googlecode.com]

Comment by tormod.s...@gmail.com:

(Man, you are quick)

[more...@googlecode.com]

Comment by michaeli...@gmail.com:

I was reading 'Reimplementing LINQ to Objects' and I wondered what had
happened to AssertSequenceEqual?

[more...@googlecode.com]

Comment by jonsk...@google.com:

It's in TestExtensions.cs, in the test project.
(I'm surprised to see AssertCount in the main project - it's not something
I'd have added myself.)

[more...@googlecode.com]

Comment by skhan....@gmail.com:

What is the difference between Pipe and ForEach? Both take an action and
repeat it over 'n' elements

For more information:
https://code.google.com/p/morelinq/wiki/OperatorsOverview

[Anders Gustafsson Cureos AB]

Return type of ForEach is void, whereas Pipe returns the enumerable on which the action has been applied. With Pipe you can thus chain multiple actions together, which will be performed sequentially on the enumerable.