Additional test cases related to bug #30568

Additional test cases related to bug #30568

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

Committed: https://github.com/dart-lang/sdk/commit/991ea77f32018ae0935cc223778329338d8b7172

[Paul Berry, 2017-08-30 20:07:55]

paulberry@google.com changed reviewers:
+ lrn@google.com

[Lasse Reichstein Nielsen, 2017-08-31 07:50:58]

LGTM!

The super-mixin problem also touches this issue, but at least that's not in the
2.0 spec, so it only affects our Flutter-compatibility flag.

[Paul Berry, 2017-08-31 17:10:03]

Description was changed from

==========
Additional test cases related to bug #30568

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.
==========

to

==========
Additional test cases related to bug #30568

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

Committed:
https://github.com/dart-lang/sdk/commit/991ea77f32018ae0935cc223778329338d8b7172
==========

[Paul Berry, 2017-08-31 17:10:04]

Committed patchset #1 (id:1) manually as
991ea77f32018ae0935cc223778329338d8b7172 (presubmit successful).

[Paul Berry, 2017-08-31 21:15:14]

On 2017/08/31 07:50:58, Lasse Reichstein Nielsen wrote:
> LGTM!
> 
> The super-mixin problem also touches this issue, but at least that's not in
the
> 2.0 spec, so it only affects our Flutter-compatibility flag.

I would love to add some tests to cover the super-mixin case as well.  Do you
know where tests of super-mixin functionality should go?

[Paul Berry, 2017-09-06 16:06:38]

On 2017/08/31 21:15:14, Paul Berry wrote:
> On 2017/08/31 07:50:58, Lasse Reichstein Nielsen wrote:
> > LGTM!
> > 
> > The super-mixin problem also touches this issue, but at least that's not in
> the
> > 2.0 spec, so it only affects our Flutter-compatibility flag.
> 
> I would love to add some tests to cover the super-mixin case as well.  Do you
> know where tests of super-mixin functionality should go?

ping