 Ian Griffiths
|
5f831de0bc
Update Ix.NET for .NET 8.0 sdk (#2135)
|
1 year ago |
 Claire Novotny
|
f1b5e96157
Update to MIT license
|
5 years ago |
 Bart De Smet
|
f329683555
Enable nullable reference types.
|
6 years ago |
 Bart De Smet
|
905f456e37
Use cached refletion info for AsyncQueryable[Ex].
|
6 years ago |
|
Bart De Smet
|
f2ce04b662
The Big Rename to avoid ambiguity between sync/async/cancellable overloads of operators.
|
6 years ago |
|
Bart De Smet
|
1a63ba15ab
Use ValueTask<T> for aggregates to improve ergonomics when used in e.g. Select.
|
6 years ago |
|
Bart De Smet
|
369026d24e
Taming CancellationToken overload hell
|
6 years ago |
|
Bart De Smet
|
c3d0ef0854
Allowing null for comparers in AsyncQueryable[Ex] surface.
|
6 years ago |
|
Bart De Smet
|
21f77a3ec9
Exclude WIthCancellation from AsyncQueryable.
|
6 years ago |
|
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.
|
7 years ago |
|
Bart De Smet
|
65e40bed85
Improve code-gen stability for queryable API surface.
|
7 years ago |
|
Bart De Smet
|
707e6e9dab
Improving AsyncQueryable codegen stability.
|
8 years ago |
|
Bart De Smet
|
a70c81c7ce
Refactoring AsyncQueryable surface.
|
8 years ago |
