You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 27, 2019. It is now read-only.
If async is present, return-type must be a type that implements Awaitable.
That is incorrect; the type must be exactly Awaitable or Awaitable for some T. An interface which extends Awaitable or a class which implements Awaitable is not legal here.
Chapter 16 does not mention at all that an async method must have a particular return type. (Though this is subtly implied by the note which says that an abstract non-async method may be awaitable.)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Chapter 10 says
If async is present, return-type must be a type that implements Awaitable.
That is incorrect; the type must be exactly Awaitable or Awaitable for some T. An interface which extends Awaitable or a class which implements Awaitable is not legal here.
Chapter 16 does not mention at all that an async method must have a particular return type. (Though this is subtly implied by the note which says that an abstract non-async method may be awaitable.)
The text was updated successfully, but these errors were encountered: