| .. |
|
Amb.cs
|
3a3c59ba42
Change signature of Clone.
|
7 年之前 |
|
Buffer.cs
|
3a3c59ba42
Change signature of Clone.
|
7 年之前 |
|
Catch.cs
|
aacb761f40
Switch to ValueTask for predicates, selectors, etc. We await those ourselves and they are expected to be called in a high-frequency manner, so this seems to be the right choice. The only drawback is when these operators are used using method group conversion of a Task-returning async method, which is likely rare in query expressions where one typically uses (async) lambdas, and there's a workaround Task-to-ValueTask conversion. We can't overload on ValueTask and Task return types, so this seems the best way forward.
|
7 年之前 |
|
Concat.cs
|
3a3c59ba42
Change signature of Clone.
|
7 年之前 |
|
Defer.cs
|
1ddf353701
Rewrite Defer to be lazy in all cases.
|
7 年之前 |
|
Distinct.cs
|
aacb761f40
Switch to ValueTask for predicates, selectors, etc. We await those ourselves and they are expected to be called in a high-frequency manner, so this seems to be the right choice. The only drawback is when these operators are used using method group conversion of a Task-returning async method, which is likely rare in query expressions where one typically uses (async) lambdas, and there's a workaround Task-to-ValueTask conversion. We can't overload on ValueTask and Task return types, so this seems the best way forward.
|
7 年之前 |
|
DistinctUntilChanged.cs
|
aacb761f40
Switch to ValueTask for predicates, selectors, etc. We await those ourselves and they are expected to be called in a high-frequency manner, so this seems to be the right choice. The only drawback is when these operators are used using method group conversion of a Task-returning async method, which is likely rare in query expressions where one typically uses (async) lambdas, and there's a workaround Task-to-ValueTask conversion. We can't overload on ValueTask and Task return types, so this seems the best way forward.
|
7 年之前 |
|
Do.cs
|
3a3c59ba42
Change signature of Clone.
|
7 年之前 |
|
Expand.cs
|
aacb761f40
Switch to ValueTask for predicates, selectors, etc. We await those ourselves and they are expected to be called in a high-frequency manner, so this seems to be the right choice. The only drawback is when these operators are used using method group conversion of a Task-returning async method, which is likely rare in query expressions where one typically uses (async) lambdas, and there's a workaround Task-to-ValueTask conversion. We can't overload on ValueTask and Task return types, so this seems the best way forward.
|
7 年之前 |
|
Finally.cs
|
3a3c59ba42
Change signature of Clone.
|
7 年之前 |
|
Generate.cs
|
3a3c59ba42
Change signature of Clone.
|
7 年之前 |
|
IgnoreElements.cs
|
3a3c59ba42
Change signature of Clone.
|
7 年之前 |
|
IsEmpty.cs
|
07a9483ed7
Share some code and streamline exceptions.
|
7 年之前 |
|
Max.cs
|
07a9483ed7
Share some code and streamline exceptions.
|
7 年之前 |
|
MaxBy.cs
|
aacb761f40
Switch to ValueTask for predicates, selectors, etc. We await those ourselves and they are expected to be called in a high-frequency manner, so this seems to be the right choice. The only drawback is when these operators are used using method group conversion of a Task-returning async method, which is likely rare in query expressions where one typically uses (async) lambdas, and there's a workaround Task-to-ValueTask conversion. We can't overload on ValueTask and Task return types, so this seems the best way forward.
|
7 年之前 |
|
Merge.cs
|
3a3c59ba42
Change signature of Clone.
|
7 年之前 |
|
Min.cs
|
07a9483ed7
Share some code and streamline exceptions.
|
7 年之前 |
|
MinBy.cs
|
aacb761f40
Switch to ValueTask for predicates, selectors, etc. We await those ourselves and they are expected to be called in a high-frequency manner, so this seems to be the right choice. The only drawback is when these operators are used using method group conversion of a Task-returning async method, which is likely rare in query expressions where one typically uses (async) lambdas, and there's a workaround Task-to-ValueTask conversion. We can't overload on ValueTask and Task return types, so this seems the best way forward.
|
7 年之前 |
|
Never.cs
|
f12d4482cc
Minor edits of Never.
|
7 年之前 |
|
OnErrorResumeNext.cs
|
3a3c59ba42
Change signature of Clone.
|
7 年之前 |
|
Repeat.cs
|
3a3c59ba42
Change signature of Clone.
|
7 年之前 |
|
Retry.cs
|
07a9483ed7
Share some code and streamline exceptions.
|
7 年之前 |
|
Return.cs
|
5e94397dee
Add support for IAsyncListProvider to Return.
|
7 年之前 |
|
Scan.cs
|
aacb761f40
Switch to ValueTask for predicates, selectors, etc. We await those ourselves and they are expected to be called in a high-frequency manner, so this seems to be the right choice. The only drawback is when these operators are used using method group conversion of a Task-returning async method, which is likely rare in query expressions where one typically uses (async) lambdas, and there's a workaround Task-to-ValueTask conversion. We can't overload on ValueTask and Task return types, so this seems the best way forward.
|
7 年之前 |
|
SelectMany.cs
|
07a9483ed7
Share some code and streamline exceptions.
|
7 年之前 |
|
StartWith.cs
|
07a9483ed7
Share some code and streamline exceptions.
|
7 年之前 |
|
Throw.cs
|
30e9bf266f
Fix Throw factory.
|
7 年之前 |
|
Timeout.cs
|
3a3c59ba42
Change signature of Clone.
|
7 年之前 |
|
Using.cs
|
aacb761f40
Switch to ValueTask for predicates, selectors, etc. We await those ourselves and they are expected to be called in a high-frequency manner, so this seems to be the right choice. The only drawback is when these operators are used using method group conversion of a Task-returning async method, which is likely rare in query expressions where one typically uses (async) lambdas, and there's a workaround Task-to-ValueTask conversion. We can't overload on ValueTask and Task return types, so this seems the best way forward.
|
7 年之前 |
Bart De Smet
aacb761f40
Switch to ValueTask for predicates, selectors, etc. We await those ourselves and they are expected to be called in a high-frequency manner, so this seems to be the right choice. The only drawback is when these operators are used using method group conversion of a Task-returning async method, which is likely rare in query expressions where one typically uses (async) lambdas, and there's a workaround Task-to-ValueTask conversion. We can't overload on ValueTask and Task return types, so this seems the best way forward.