Skip to content

SuperFormalParameter with explicit type cannot be parsed #47951

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.

Sign up for GitHub

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

Jump to bottom
Closed
scheglov opened this issue Dec 16, 2021 · 0 comments
Closed

SuperFormalParameter with explicit type cannot be parsed #47951

scheglov opened this issue Dec 16, 2021 · 0 comments
Assignees
@chloestefantsova
Labels
legacy-area-front-end Legacy: Use area-dart-model instead.

Comments

@scheglov
Copy link
Contributor 

class A {
  A(num a);
}

class B extends A {
  B.sub1(int super.a1);
  B.sub2(double super.a2);
}

image
@chloestefantsova
@scheglov scheglov added the legacy-area-front-end Legacy: Use area-dart-model instead. label Dec 16, 2021
copybara-service bot pushed a commit that referenced this issue Jan 4, 2022
@scheglov
Partial fix for parsing explicitly typed super formal parameters.
2766add 
I need at least this much to cover a few test cases in the analyzer,
but it might be not the best implementation. It seems to not break
anything, so maybe we can land this for now, while we are waiting for
the better fix of the referenced issue?

Bug: #47951
Change-Id: I428e32f4435b3229cb2dc41678182cde0e2f98e8
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/226200
Reviewed-by: Chloe Stefantsova <[email protected]>
Commit-Queue: Konstantin Shcheglov <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chloestefantsova chloestefantsova

Labels
legacy-area-front-end Legacy: Use area-dart-model instead.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@scheglov @chloestefantsova