| .. |
|
AsyncEnumerableExecutor.cs
|
a70c81c7ce
Refactoring AsyncQueryable surface.
|
8 жил өмнө |
|
AsyncEnumerableQuery.cs
|
e960ee0560
Minor code modernization.
|
7 жил өмнө |
|
AsyncEnumerableRewriter.cs
|
e960ee0560
Minor code modernization.
|
7 жил өмнө |
|
AsyncQueryable.Generated.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 жил өмнө |
|
AsyncQueryable.Generated.tt
|
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 жил өмнө |
|
AsyncQueryable.cs
|
741e9660c8
merge from master
|
7 жил өмнө |
|
IAsyncQueryProvider.cs
|
3635f00c32
Some code cosmetics.
|
8 жил өмнө |
|
IAsyncQueryable.cs
|
3635f00c32
Some code cosmetics.
|
8 жил өмнө |
|
IOrderedAsyncQueryable.cs
|
3635f00c32
Some code cosmetics.
|
8 жил өмнө |
|
LocalQueryMethodImplementationTypeAttribute.cs
|
da30f71a27
Adding LocalQueryMethodImplementationTypeAttribute support.
|
8 жил өмнө |
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.