Non-nullability gets lost with shouldBeSuccess matcher

[sschuberth]

This looks like a bug to me:

kotest/kotest-assertions/kotest-assertions-core/src/commonMain/kotlin/io/kotest/matchers/result/matchers.kt

Line 9 in c64f888

fun <T> Result<T>.shouldBeSuccess(block: ((T?) -> Unit)? = null) {

If the result is of type T (non-nullable), why is the block then called with the nullable type T??

[sschuberth]

shouldBeFailure has a similar problem:

kotest/kotest-assertions/kotest-assertions-core/src/commonMain/kotlin/io/kotest/matchers/result/matchers.kt

Lines 20 to 23 in c64f888

	fun Result<Any?>.shouldBeFailure(block: ((Throwable?) -> Unit)? = null) {
	this should BeFailure()
	block?.invoke(this.exceptionOrNull()!!)
	}

The block is explicitly invoked with the not-null assertion operator (!!), but still the signature says Throwable?.