Comments on: Another source for LINQ extensions http://lostechies.com/jimmybogard/2011/03/08/another-source-for-linq-extensions/ Strong opinions, weakly held Sun, 19 May 2013 03:22:18 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Pablo Montilla http://lostechies.com/jimmybogard/2011/03/08/another-source-for-linq-extensions/#comment-3270 Pablo Montilla Fri, 01 Apr 2011 13:22:00 +0000 /blogs/jimmy_bogard/archive/2011/03/08/another-source-for-linq-extensions.aspx#comment-3270 In which ways is Partition() different from System.Linq.EnumerableEx.BufferWithCount() in System.Interactive? In which ways is Partition() different from System.Linq.EnumerableEx.BufferWithCount() in System.Interactive?

]]> By: Johannes Rudolph http://lostechies.com/jimmybogard/2011/03/08/another-source-for-linq-extensions/#comment-2856 Johannes Rudolph Tue, 08 Mar 2011 22:33:27 +0000 /blogs/jimmy_bogard/archive/2011/03/08/another-source-for-linq-extensions.aspx#comment-2856 Being one of the guys who worked on that particular piece of code, I can tell you a couple of things about Partition(): a) It's not fully finished yet (it's in the EvenMoreLinq branch which sort of serves as a staging area). There are issues (such as when using it with an infinte sequence of partition sizes) b) The source sequence is lazily evaluated, a partition is buffered before it is returned. A buffered partition is returned element by element. peSHIr's implementation will always yield the buffered parition in one go (the full list). Implementing LINQ operators is actually not quite as easy as it seems in the first place. The issue we had with MoreLinq is the lack of real world feedback, both in terms of desired features as well as desired behavior, so a lot of ideas we had ended up in that staging area. The second aspect is that most operators there haven't been performance optimized yet, Parition is a good example for that. There's a lot of headroom for making it faster such as adding selectors, tweaking the buffer and properly letting go of it. Being one of the guys who worked on that particular piece of code, I can tell you a couple of things about Partition():

a) It’s not fully finished yet (it’s in the EvenMoreLinq branch which sort of serves as a staging area). There are issues (such as when using it with an infinte sequence of partition sizes)
b) The source sequence is lazily evaluated, a partition is buffered before it is returned. A buffered partition is returned element by element.

peSHIr’s implementation will always yield the buffered parition in one go (the full list).

Implementing LINQ operators is actually not quite as easy as it seems in the first place. The issue we had with MoreLinq is the lack of real world feedback, both in terms of desired features as well as desired behavior, so a lot of ideas we had ended up in that staging area.

The second aspect is that most operators there haven’t been performance optimized yet, Parition is a good example for that. There’s a lot of headroom for making it faster such as adding selectors, tweaking the buffer and properly letting go of it.

]]> By: Johannes Rudolph http://lostechies.com/jimmybogard/2011/03/08/another-source-for-linq-extensions/#comment-2855 Johannes Rudolph Tue, 08 Mar 2011 22:32:42 +0000 /blogs/jimmy_bogard/archive/2011/03/08/another-source-for-linq-extensions.aspx#comment-2855 Being one of the guys who worked on that particular piece of code, I can tell you a couple of things about Partition(): a) It's not fully finished yet (it's in the EvenMoreLinq branch which sort of serves as a staging area). There are issues (such as when using it with an infinte sequence of partition sizes) b) The source sequence is lazily evaluated, a partition is buffered before it is returned. A buffered partition is returned element by element. peSHIr's implementation will always yield the buffered parition in one go (the full list). Implementing LINQ operators is actually not quite as easy as it seems in the first place. The issue we had with MoreLinq is the lack of real world feedback, both in terms of desired features as well as desired behavior, so a lot of ideas we had ended up in that staging area. The second aspect is that most operators there haven't been performance optimized yet, Parition is a good example for that. There's a lot of headroom for making it faster such as adding selectors, tweaking the buffer and properly letting go of it. Being one of the guys who worked on that particular piece of code, I can tell you a couple of things about Partition():

a) It’s not fully finished yet (it’s in the EvenMoreLinq branch which sort of serves as a staging area). There are issues (such as when using it with an infinte sequence of partition sizes)
b) The source sequence is lazily evaluated, a partition is buffered before it is returned. A buffered partition is returned element by element.

peSHIr’s implementation will always yield the buffered parition in one go (the full list).

Implementing LINQ operators is actually not quite as easy as it seems in the first place. The issue we had with MoreLinq is the lack of real world feedback, both in terms of desired features as well as desired behavior, so a lot of ideas we had ended up in that staging area.

The second aspect is that most operators there haven’t been performance optimized yet, Parition is a good example for that. There’s a lot of headroom for making it faster such as adding selectors, tweaking the buffer and properly letting go of it.

]]> By: Frank Quednau http://lostechies.com/jimmybogard/2011/03/08/another-source-for-linq-extensions/#comment-2854 Frank Quednau Tue, 08 Mar 2011 22:22:47 +0000 /blogs/jimmy_bogard/archive/2011/03/08/another-source-for-linq-extensions.aspx#comment-2854 Reactive works off IObservable<T>, so you really should have both ;) Reactive works off IObservable, so you really should have both ;)

]]> By: peSHIr http://lostechies.com/jimmybogard/2011/03/08/another-source-for-linq-extensions/#comment-2853 peSHIr Tue, 08 Mar 2011 14:56:49 +0000 /blogs/jimmy_bogard/archive/2011/03/08/another-source-for-linq-extensions.aspx#comment-2853 Ah, the little morsel I chose to call SplitUp. I guess, if it's written by Jon Skeet (or another rock-star author ;-)), that Partition is just as lazy in it's behavior as my http://peshir.blogspot.com/2011/03/example-code-for-splitup-on-infinite.html is? Ah, the little morsel I chose to call SplitUp. I guess, if it’s written by Jon Skeet (or another rock-star author ;-) ), that Partition is just as lazy in it’s behavior as my http://peshir.blogspot.com/2011/03/example-code-for-splitup-on-infinite.html is?

]]>