 Bart De Smet
|
ca0a8b53b4
Change CSHARP8 for USE_* checks. Enable C# 8.0 for all builds.
|
6 years ago |
|
Bart De Smet
|
e576f23303
Remove AETOR_HAS_CT checks. CancellationToken is now supported on the interface.
|
6 years ago |
|
Bart De Smet
|
971f38e22d
Use C# 8.0 in Lookup.
|
6 years ago |
|
Bart De Smet
|
c6da267eef
Remove duplicate accesses to Current in Lookup.
|
6 years ago |
 Oren Novotny
|
b9f9514d57
Revert "Use only var when type is obvious."
|
6 years ago |
|
Bart De Smet
|
876ee400a9
Use only var when type is obvious.
|
6 years ago |
|
Bart De Smet
|
aa2430bb42
Check for cancellation in a few more places.
|
6 years ago |
|
Bart De Smet
|
ce1cc00303
Use ValueTask in a few more places.
|
6 years ago |
|
Bart De Smet
|
8b7d90e758
Embrace LDM-2018-11-28 decision to check for cancellation in GetAsyncEnumerator.
|
6 years ago |
|
Bart De Smet
|
d596d9f6d8
Adding "deep cancellation" API surface predicated by a NO_DEEP_CANCELLATION symbol.
|
7 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
|
1776af560f
Move Lookup types to separate file.
|
7 years ago |
