mirror of
https://github.com/dart-lang/sdk
synced 2024-09-18 21:21:18 +00:00
991ea77f32
These test cases verify that when a method calls super, compile-time arity checks are performed against the actual target of super, rather than the interface exposed by the base class. R=lrn@google.com Review-Url: https://codereview.chromium.org/3005893002 .
35 lines
823 B
Dart
35 lines
823 B
Dart
// Copyright (c) 2017, the Dart project authors. Please see the AUTHORS file
|
|
// for details. All rights reserved. Use of this source code is governed by a
|
|
// BSD-style license that can be found in the LICENSE file.
|
|
|
|
class A {
|
|
void foo() {}
|
|
}
|
|
|
|
abstract class I {
|
|
void foo([x]);
|
|
}
|
|
|
|
abstract class B extends A implements I {
|
|
// If this class were concrete, there would be a problem, since `new
|
|
// B().foo(42)` would be statically allowed, but would lead to invalid
|
|
// arguments being passed to A.foo. But since the class is abstract, there is
|
|
// no problem.
|
|
}
|
|
|
|
class C extends B {
|
|
void foo([x]) {
|
|
// But it is a problem to try to pass `x` along to super, since the super
|
|
// method is A.foo.
|
|
super.foo(/*@compile-error=unspecified*/ x);
|
|
}
|
|
}
|
|
|
|
void f(B b) {
|
|
b.foo(42);
|
|
}
|
|
|
|
main() {
|
|
f(new C());
|
|
}
|