I have 2 methods

fun <ACTUAL> expect(
  actual: ACTUAL,
  block: ObjectAssert<ACTUAL>.(ACTUAL) -> Unit
): ObjectAssert<ACTUAL>

and

fun <ELEMENT> expect(
  actual: List<ELEMENT>,
  block: SoftAssertionListAssert<ELEMENT>.(List<ELEMENT>) -> Unit
): SoftAssertionListAssert<ELEMENT>

that the compiler is unable to distinguish between at the call site. I get why that’s an issue but confusingly I have overloads of both that only accept the first parameter:

fun <ACTUAL> expect(actual: ACTUAL): AbstractObjectAssert<*, ACTUAL>

and

fun <ELEMENT> expect(actual: List<ELEMENT>): ListAssert<ELEMENT>

that the compiler can distinguish. Can anyone enlighten me as to why one is a problem and no the other? Is there any way I can disambiguate the 2 param form?

Is there an inheritance relation between

SoftAssertionListAssert

and

ObjectAssert

?

@robfletcher can you give us an example how you try to invoke

expect

?

I was wondering about the inheritance relationship but no there is not.

@robfletcher do you pass a lambda as the second parameter?

yes

@robfletcher the problem is, that the kotlin-compiler needs to know the inputs/outputs of a lambda before it checks the body of the lambda. Thats why declaring the lambda before works. I don't really see a way around that apart from renaming one of the methods

yeah, it makes sense