Strong mode errors while pub upgrade

[Aetet]

Hi.
At our project we did not use matcher directly but we depend on it from quiver and test packages.

Recently after pub upgrade unit tests at our project failed, because of strong mode errors. pub upgrade bring new version of matcher. Method signatures was changed at:
dart-archive/matcher#61

Is it possible to use semver for such changes, because it can break external projects?

[nex3]

Can you give an example of code that was broken by dart-archive/matcher#61?

[Aetet]

Hi @nex3, here is an example:

      verify(track.fire('event_track', argThat(predicate((dynamic args) {

Before that there's no generic for predicate function,after pub upgrade there's error:

severity: 'Error'
message: 'Missing type arguments for generic function 'predicate<T>'.'
source: 'dart'

so after pub upgrade some builds failed. Fix is trivial, but it takes some time to make it work again.

[nex3]

Sorry, I should have been clearer. Can you provide a full Dart program that only depends on matcher and worked before dart-archive/matcher#61 and not after?

[kevmoo]

@Aetet – is this still an issue?