-
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
[CP] Avoid CFE crash when input contains invalid super parameters usage #50052
Comments
@johnniwinther @vsmenon @athomas @sigmundch thoughts on this cherry-pick? |
LGTM |
lgtm |
SGTM |
Marking this as approved. If anyone has a major reason why this shouldn't happen, please note it here. |
We should also merge this fix to beta, it missed the branchout. |
Bug: #50052 Change-Id: I1d9aedac81b2fdb05f04a0246d1088ffa66192ef Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/261300 Reviewed-by: Alexander Thomas <athom@google.com>
Bug: #50052 Change-Id: I1d9aedac81b2fdb05f04a0246d1088ffa66192ef Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/261300 Reviewed-by: Alexander Thomas <athom@google.com>
Merged to stable 2.18.2, not closing until it is fixed on beta as well. |
@itsjustkevin If we don't plan another beta before the beta 2 branchout, this issue alone doesn't seem enough to warrant a new beta build (given that beta 2 is not too far in the future). |
Fair point @athomas if it turns out to be a big callout, we can pivot. |
Closing issue - it is landed in stable, and will be in the new beta branchout created today. |
Commit(s) to merge
bbdb9e4
Target
stable
Issue Description
CFE crashes when input contains incorrect usage of super parameters feature instead of reporting a syntax error.
What is the fix
Fix global type inference to propertly handle situations where incorrect super parameters are involved.
Why cherry-pick
Users get an uninformative CFE crash with a stack trace instead of a readable syntax error and can't really figure out what is wrong with their code on their own.
Risk
low
Issue link(s)
#49641
flutter/flutter#111833
#47470 (comment)
Extra Info
No response
The text was updated successfully, but these errors were encountered: