tree 26092cb4680ddcd89f4c27ffdd53df38c9d78cac
parent e73c76a7a290b797a7d842cfbf8af712b64caf35
author Michael R Fairhurst <michaelrfairhurst@gmail.com> 1517284507 -0800
committer Sam Rawlins <sam.rawlins@gmail.com> 1517284507 -0800

Capture T in `verify`+ so T may be `void` in dart 2: `verify(m.void())` (#90)

Capture T in `verify`+ so T may be `void` in dart 2: `verify(m.void())`

While the semantics here are not yet fully decided, it is likely that
dart 2 will disallow passing void into dynamic. The most backwards
compatible solution here is to parameterize meta function types over T
so that the type `void` is inferred, *possibly* allowing the result of a
void method to be passed in.

This change unblocks us for incrementally rolling out the new void
semantics.

It may in fact require a change to specify the `void` type directly,
rather than allowing `T` to be void for any `T`, but for now that's not
required and would hurt backwards compatibility since `void` didn't used
to be allowed there.

It also may not be allowed at all under any case, in which case we'd be
in for a fun ride.