Mock does not conform to protocol when functions differ only in their return type about swiftymocky HOT 6 CLOSED

Thank you! It works perfectly 😊

from swiftymocky.

@andlang
Thanks for rising issue, i belive this was resolved, and we had this case covered in ingegration tests.

We will try to fix this issue ASAP and release new minor version.

Just FYI, along with rised issues, you can also submit PR with failing tests for some unnusual cases :)

from swiftymocky.

@andlang - looking into it, will try to have it covered until beginning of next week

from swiftymocky.

OK, so this will require further concept work. First of all - even if we can avoid ambiguity by specifying return type, like:

let strVal: String = mock.foo(bar: "str") // method called that returns string
let intVal: Int = mock.foo(bar: "int")  // method called that returns int

That leaves us with question - what to do for perform and verify?

The typical usage will be:

Verify(mock, .foo(bar: .any))

Does it applies to both methods? Should it apply to both methods?

We can try some more advanced syntax for that particular case, like:

Verify(mock, .foo(bar: .any, returning: String.self))
Verify(mock, .foo(bar: .any, returning: Int.self))

What do you guys think?

from swiftymocky.

@andrzejmichnia the solution you proposed seems to be nice and clear, how about other return types, like tuple?

from swiftymocky.

Thank you for replying so fast!
This solution with the returning parameter seems good for me!

from swiftymocky.