-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C# 7.x 15.15.1 standard library task types #844
Comments
Hmm... it's interesting that we mention |
- Use `Task<TResult>` everywhere instead of `Task<T>` - Fix typo around which type is generic and which isn't Fixes dotnet#844.
ValueTask and ValueTask<TResult> will be needed in C# 8 async streams #606: |
- Use `Task<TResult>` everywhere instead of `Task<T>` - Fix typo around which type is generic and which isn't Fixes dotnet#844.
- Use `Task<TResult>` everywhere instead of `Task<T>` - Fix typo around which type is generic and which isn't Fixes dotnet#844.
- Use `Task<TResult>` everywhere instead of `Task<T>` - Fix typo around which type is generic and which isn't Fixes #844.
Describe the bug
In the C# 7 draft, 15.15.1 says
However, there cannot be any types constructed from
System.Threading.Tasks.Task
, because it is not a generic type.Example
None
Expected behavior
Additional context
Could also mention ValueTask and ValueTask<T>, which are listed in C.3 (Standard Library Types not defined in ISO/IEC 23271).
C.3 is inconsistent on whether the type parameter of these is named
T
orTResult
. This name is not used when referencing the type in C#, but it is stored in the ECMA-335 GenericParam table and may be readable by reflection.The text was updated successfully, but these errors were encountered: