Atif Aziz

Based on work so far in PR #753, I feel it's best to rename the extension to `SpillHead`. The simplest overload will spill the first element of the sequence to...

[`TraverseDepthFirst`](https://morelinq.github.io/2.0/ref/api/html/M_MoreLinq_MoreEnumerable_TraverseDepthFirst__1.htm) can help with this to a large extent. For example, your recursive types example can be written like this: ```c# var example1 = from c in categories where c.Parent...

I'd also like to add that this method isn't the opposite of [`Flatten`](https://morelinq.github.io/2.10/ref/api/html/Overload_MoreLinq_MoreEnumerable_Flatten.htm) even if it _feels_ so. While `Flatten` traverses a nested sequence in depth-first order and lays them...

I am afraid we have not fleshed this out enough. I still have to come back to you with some comments on [your last reply](https://github.com/morelinq/MoreLINQ/issues/477#issuecomment-385559426).

> For performance reason, I think that the MoreLinq methods should not call other MoreLinq methods but go straightforward to the most efficient implementation. Yes, I agree with that. In...

@leandromoh That test can never work. Note the remarks comments: ```c# /// /// This method uses deferred execution semantics but iterates the /// entirely when either of the sequences ///...

@leandromoh So you completely changed the implementation to make it work with infinite sources. I'd say it's a little detail you missed out [earlier](https://github.com/morelinq/MoreLINQ/pull/316#issuecomment-308775281). 😆 I have a hard time...

Love that quote by Hoare every time I read it. > Since my draft passed in all wroten test, I suppose it is a perfectly valid implementation. True, but aren't...

@leandromoh Not much news, I'm afraid. 😞 I don't know if you followed #337, but I think [the idea of using a reader monad to express partial consumption](https://github.com/morelinq/MoreLINQ/issues/337#issuecomment-320438526) would work...

2a094a87fda3b268fb68b1a4954d7298b8b0ad93 updates the implementation based on [my revised proposal for #315](https://github.com/morelinq/MoreLINQ/issues/315#issuecomment-379003305) where split parts are returned as sub-sequences instead of a pivoted couple (tuple of 2) of parts. :memo: Notes:...