Skip to content

Some mixin tests are missing compile errors when run in DDC #34516

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
jmesserly opened this issue Sep 18, 2018 · 3 comments
Closed

Some mixin tests are missing compile errors when run in DDC #34516

jmesserly opened this issue Sep 18, 2018 · 3 comments
Labels
legacy-area-analyzer Use area-devexp instead. P1 A high priority bug; for example, a single project is unusable or has many test failures
Milestone

Comments

@jmesserly
Copy link

from @leafpetersen:

I landed inference tests, and I'm seeing some tests that are expected to produce a compile time error and which are passing on the analyzer, failing on ddc. This seems unexpected so re-opening this for investigation.

mixin_declaration/mixin_declaration_inference_invalid_03_test: MissingCompileTimeError   # https://github.com/dart-lang/sdk/issues/34167
mixin_declaration/mixin_declaration_inference_invalid_04_test: MissingCompileTimeError   # https://github.com/dart-lang/sdk/issues/34167
mixin_declaration/mixin_declaration_inference_invalid_05_test: MissingCompileTimeError   # https://github.com/dart-lang/sdk/issues/34167
mixin_declaration/mixin_declaration_inference_invalid_06_test: MissingCompileTimeError   # https://github.com/dart-lang/sdk/issues/34167
mixin_declaration/mixin_declaration_inference_invalid_07_test: MissingCompileTimeError   # https://github.com/dart-lang/sdk/issues/34167
mixin_declaration/mixin_declaration_inference_invalid_08_test: MissingCompileTimeError   # https://github.com/dart-lang/sdk/issues/34167
mixin_declaration/mixin_declaration_inference_invalid_09_test: MissingCompileTimeError   # https://github.com/dart-lang/sdk/issues/34167
mixin_declaration/mixin_declaration_inference_invalid_10_test: MissingCompileTimeError   # https://github.com/dart-lang/sdk/issues/34167
@jmesserly jmesserly added the legacy-area-analyzer Use area-devexp instead. label Sep 18, 2018
@jmesserly jmesserly added this to the Dart2.1 milestone Sep 18, 2018
@jmesserly jmesserly self-assigned this Sep 18, 2018
@jmesserly jmesserly added the P1 A high priority bug; for example, a single project is unusable or has many test failures label Sep 18, 2018
@jmesserly
Copy link
Author

This is almost certainly Analyzer side (DDC does not produce errors) but I'll take a look. Could be task model or summary related.

@jmesserly
Copy link
Author

jmesserly commented Sep 18, 2018

conflicting interfaces are not reported because DDC is on the task model.

Error verifier has this:

  /// Setting this flag to `true` disables the check for conflicting generics.
  /// This is used when running with the old task model to work around
  /// dartbug.com/32421.
  ///
  /// TODO(paulberry): remove this flag once dartbug.com/32421 is properly
  /// fixed.
  final bool disableConflictingGenericsCheck;

Which references this issue:
#32421

Which @stereotype441 and @leafpetersen talked about in these comments:
#32421 (comment)

From that discussion, it sounds like we are OK with DDC missing the conflicting interface errors until DDC switches to Kernel.

I believe the right resolution is to close this, as it is not related to mixins per se, but to the existing decision around conflicting interface errors in Analyzer. Let me know if that has changed, or if I misunderstood anything about that discussion.

(FYI -- I am rapidly making progress on removing the DDC's Analyzer backend, and also in parallel, I have a local change that switches DDC over to Analysis Driver. But my current focus is on DDC's Kernel backend.)

@jmesserly jmesserly removed their assignment Sep 18, 2018
@leafpetersen
Copy link
Member

SGTM, thanks for taking a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy-area-analyzer Use area-devexp instead. P1 A high priority bug; for example, a single project is unusable or has many test failures
Projects
None yet
Development

No branches or pull requests

2 participants