-
Notifications
You must be signed in to change notification settings - Fork 164
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
Support for extension-type/inline-class #732
Comments
EDIT: uh, actually the feature is already there. Yep, I will have to find time to add the support then. |
The version at HEAD should now cover the "method returns an extension type" case. We'll do a release soon. |
@yanok what's the status of releasing this? |
This should be reopened until a release is made. |
Extension types were released in Dart 3.3.0. Is there still an issue with mockito, can it be demonstrated by a small example? In that case the issue should certainly be reopened (or a new issue could be created), if it isn't already reported in some other issue. (I'm not working on mockito, I just wanted to mention that the extension type feature is in the language today.) |
Basic extension type support was introduced because of this issue, but has not yet been published on pub as there has been no release for almost a year. Support for extension types with generics does not yet exist, even on the main branch. A code example for the not working case of an extension type with generics is in issue: #755 |
Thanks! I asked around a bit to see if somebody can say more. |
What has stopped a release since February? Should package users expect one at all? |
It's probably too early and/or too minor, but would it be possible to already support extension types (like with
-nullsafety
)? The experiment has been enabled by default in the Dart dev version for a while now.For example, if I have a getter returning an extension type, this is what I get:
And I'm just seeing this, but there is a typo in the error message. It should be "neither" not "nether".
The text was updated successfully, but these errors were encountered: