Skip to content

Failures on [cfe] Add ClassMember.memberKind and .getTearOff #53901

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

Closed
johnniwinther opened this issue Oct 30, 2023 · 4 comments
Closed

Failures on [cfe] Add ClassMember.memberKind and .getTearOff #53901

johnniwinther opened this issue Oct 30, 2023 · 4 comments
Labels
cfe-feature-extension-types Implement extension types feature in the CFE legacy-area-front-end Legacy: Use area-dart-model instead.

Comments

@johnniwinther
Copy link
Member

There are new test failures on [cfe] Add ClassMember.memberKind and .getTearOff.

The tests

co19/LanguageFeatures/Extension-types/superinterfaces_of_extension_type_A05_t07 CompileTimeError (expected Pass)

are failing on configurations

cfe-strong-linux
cfe-weak-linux
dart2wasm-linux-chrome
dart2wasm-linux-d8
vm-mac-debug-arm64
vm-mac-release-arm64
@johnniwinther johnniwinther added legacy-area-front-end Legacy: Use area-dart-model instead. cfe-feature-extension-types Implement extension types feature in the CFE labels Oct 30, 2023
@johnniwinther
Copy link
Member Author

@eernstg Do we have any specification on whether/when we should report errors on property/method and getter/setter conflicts in extension types? I can't seem to guess what co19 expects.

@eernstg
Copy link
Member

eernstg commented Oct 30, 2023

The test co19/LanguageFeatures/Extension-types/superinterfaces_of_extension_type_A05_t07 should be updated, because it expects no errors in a situation where there is a setter/getter signature conflict (and they should be reported here, just as they are reported for classes etc.).

This test is presumably intended to verify that there is no constraint like the override correctness that we enforce with class member override relations. In particular, it's OK to redeclare a getter (in this case: an implicitly induced external getter) as a method.

It looks like the setter/getter signature conflict is an accident, and in that case the test could just use external final int id2; to avoid introducing the setter in the first place.

@eernstg
Copy link
Member

eernstg commented Oct 30, 2023

I created a co19 issue here: dart-lang/co19#2335.

@johnniwinther
Copy link
Member Author

The test has now been updated and matches our expectations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cfe-feature-extension-types Implement extension types feature in the CFE legacy-area-front-end Legacy: Use area-dart-model instead.
Projects
None yet
Development

No branches or pull requests

2 participants