-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Stop reporting the getter/setter type error #58578
Comments
For the CFE this is a fairly simple change which we could include in 3.8. (We are too close to 3.7 beta 2 cutoff). |
Removing the reporting of this diagnostic should be very little work. I'm comfortable committing to the 3.8 build.
And also so that the CFE and analyzer are in sync with each other. It would be bad for users if one reported an error when the other didn't. |
It's a language versioned change, so the release will be synchronized no matter when it can be done. |
The CL creating the flag is in review: https://dart-review.googlesource.com/c/sdk/+/396581 |
That's great, thanks! |
Part of #58578 Change-Id: I819d4b86761f60d59a8aa95a1dfba1c280499992 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/396581 Reviewed-by: Michael Thomsen <[email protected]> Reviewed-by: Erik Ernst <[email protected]> Reviewed-by: Konstantin Shcheglov <[email protected]> Reviewed-by: Johnni Winther <[email protected]> Commit-Queue: Chloe Stefantsova <[email protected]>
Based on dart-lang/language#2809, the error which is reported when a getter has a return type which is not a subtype of the parameter type of the corresponding setter should no longer be reported. That is, this situation is no longer an error.
Subtasks:
This change needs to be language versioned because it enables certain declarations that weren't previously allowed.
@bwilkerson, @johnniwinther, can you suggest a good schedule for doing this?
The text was updated successfully, but these errors were encountered: