Meta issue tracking analyzer Dart 2.0 type system inconsistencies

[leafpetersen]

This issue is a meta-issue to track places where the new front end and the analyzer (using the analyzer driver's resolution) disagree.

Update: Open issues

• Instantiate to bounds usage is self-inconsistent: Analyzer instantiate to bounds for typedefs is inconsistent #32114
• type parameters on const values Analyzer does not eliminate type variables from const values #32918
• Generic function types shouldn't be type arguments: Analyzer: it is an error if a type argument is a generic function type #33343
• Carry over of 33343 (generic function types): Analyzer: don't infer generic function types as type parameters #33661
• Subtyping on type bounds: Bounds on generic methods should be treated invariantly in subtyping #29014 @MichaelRFairhurst
• Reserve mixin and identifier: Analyzer: mixin and interface should be builtin identifiers in Dart 2 #33131
• Type variable conflation: Analyzer issue with complex generic functions #33159
• Bad typing with generic call method: Callable class has incorrect return type #33194
• Future flattening shouldn't be recursive: Analyzer shouldn't recursively flatten futures #32881
• Missing error when awaiting a void expression: Missing error when awaiting a void expression #33415
• Error with function type syntax in generics: Cannot use new Function syntax in const Map declaration #32933
• Partial instantiations in default values: Analyzer does not reject non-const partial instantiations for default parameter values #32913
• Inconsistent call method tearoffs: Inconsistent call method tearoff behavior between analyzer and CFE #32864
• Prefix scoping: Prefix names are lexically scoped. #32248
• Invalid Function syntax is allowed Analyzer allows function type parameters in new Function syntax #33398
• Super bounded types: Dartanalyzer 2.0 incorrectly throws type_argument_not_matching_bounds error for super-bounded types in preview-dart-2 mode #32903
• Methods on null Analyzer: null.foo reports no warning #27273
• Restrict partial instantiation to known targets: Strong mode implicit generic instantiations should be limited to known targets #28162
• Abstract super calls: Analyzer/CFE inconsistency on super calls to abstract methods. #33662
• Top types and LUB: Analyzer: move void above (below) dynamic in LUB(GLB) #33341

Blocking issues (in the beta 3 timeframe):

• Top level inference doesn't work with optional new: Analyzer top level inference doesn't work with optional new/const #32397
• Analyzer summary type logic doesn't do downward type inference Analyzer summary type logic doesn't do downward type inference #32525
  • Silent top level inference inconsistency: Silent inconsistency in top level inference #32394
• move flutter analyze off the task model: move flutter analyze off of the task model #32478 @devoncarew
• Restrict behavior of callable classes - analyzer implementation Restrict behavior of callable classes - analyzer implementation #32156 @jmesserly

Non-blocking open issues:

• Inference of generic tearoff on field: Initializing a field with a generic static method tearoff causes type error  #32396
• Redirecting constructors: Redirecting factory constructors don't propagate generic type arguments #30855
• Inconsistencies in downwards inference: Analyzer and CFE inference disagreement #32305
• Instantiate to bounds at ground type: Raw types in bounds should be allowed when the raw type bound is ground #28580 @michaelrfarhurst
• .call is not checked: Using .call to call a function is not checked in strong mode #27098
• Remove support for fuzzy arrows from the analyzer Remove support for fuzzy arrows from the analyzer #31637
• Try to make returning void within dynamic an error Try to make returning void within dynamic an error #32161

--

cc @devoncarew @stereotype441 @scheglov @bwilkerson

[leafpetersen]

I'm doing some preliminary triage above, feel free to adjust or move around.

[devoncarew]

This will likely be needed by mid-April.

[dgrove]

Note that blocking issues #32305 and #32156 are targeted at Dart 2-Beta 4, while this issue is targeted at Beta 3.

[leafpetersen]

I'm putting stable as the milestone for the meta-issue.

[MichaelRFairhurst]

Updated to mark ".call is not checked: #27098" fixed

[bwilkerson]

@leafpetersen Is this list complete? Is it up to date? Is everything on it still needed for stable? What priority should it have?

[leafpetersen]

@bwilkerson @devoncarew I just did a quick triage pass on open issues looking for 2.0 type system issues and added bullets above in approximate priority order. I'll do some more triage next week. I wouldn't say any of these are strictly blockers, but the top few at least would be good to fix before 2.0.

[bwilkerson]

@leafpetersen This issue is out of date. I have made sure that all of the still open issues listed above have the 2.1 milestone associated with them. Given that, I'm going to close it, but feel free to re-open it if you think it's still useful.