Clarify the semantics of tearing off an inherited abstract method

[bwilkerson]

I have the following code:

abstract class A {
  void test();
}
class B extends A {
  void test() {
    super.test; // code in question
  }
}

Dart analyzer does not produce any static errors, but the CFE is currently issuing an error indicating that the class A does not define a getter named test. I couldn't find any place in the spec that would indicate that this should be an error. In particular, section 16.19.2 "Super Getter Access and Method Closurization" appears to indicate that this should be valid.

Should this code produce an error?

If so, then I'll open an analyzer issue. If not, then I'll open a CFE issue.

[chloestefantsova]

Note that CFE only produces error if class B is not abstract and enableSuperMixins is false; it compiles the program successfully otherwise.

[chloestefantsova]

/cc @leafpetersen @eernstg

[leafpetersen]

Yes, this should be an error. See also #33662 .

[leafpetersen]

Filed a spec bug to make sure the text reflects this: #33963 .

[eernstg]

Fixed in #33963.