Orace
Orace
`Dispatch` #633 may have been used to implement this.
Fix #366
Addressed in zip refactoring #639 and in #598
> > Fixed in #639 > > Correction: this is being addressed in PR #598. It is _not fixed_ unless a PR is merged into the master branch and neither...
A first step is to use the `Disposable/Acquire` combo in `Transpose` and `Interleave`.
As explained [here](https://github.com/morelinq/MoreLINQ/pull/696#discussion_r357024290), `Acquire` and `ToDisposableLinkedList` will eagerly call `GetEnumerator`. And with this behavior, the code below will throw (it doesn't in #726): ```C# var sequenceA = Enumerable.Range(1, 1); var...
A solution is to build hand crafted implementation for every methods and prohibit nested enumerable ;)
`WindowLeft` and `WindowRight` stay the recommended choice for _static_ cases. `Window(int size)` is preserved. We add possibility for dynamic choice. I do think that the best way to write it...
Those tests are useful to correctly fix #729 that is addressed in #730.
An other option is to made `Window` _relaxed_ (ie: behave like `WindowLeftAndRight`) and introduce `Strict` method. {Lead|Lag|Window}{_|Left|Right|Strict} This is a breaking change for current `Window` behavior.