You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've just tried upgrading from strikt 0.33 to strikt 0.34. It's a kotlin-JVM project with Kotlin 1.6.10.
In strikt 0.34, a second overload of the IsNotNull method was introduced:
/** * noop not null assertion on not nullable receiver*/
@JvmName("isNotNullT?")
fun <T:Any> Builder<T>.isNotNull(): Builder<T> =this
The existence of this overload causes issues for the kotlin compiler. Code which worked fine on strikt 0.33 doesn't compile with 0.34 anymore because of this overload (Kotlin: [Internal Error] org.jetbrains.kotlin.util.KotlinFrontEndException: Exception while analyzing expression at ...)
The text was updated successfully, but these errors were encountered:
In theory it should be possible to define a single isNotNull method that works on both nullable and non-nullable types, right? Or is the generic typebound on Builder<T> getting in the way?
I've just tried upgrading from strikt 0.33 to strikt 0.34. It's a kotlin-JVM project with Kotlin 1.6.10.
In strikt 0.34, a second overload of the
IsNotNull
method was introduced:The existence of this overload causes issues for the kotlin compiler. Code which worked fine on strikt 0.33 doesn't compile with 0.34 anymore because of this overload (
Kotlin: [Internal Error] org.jetbrains.kotlin.util.KotlinFrontEndException: Exception while analyzing expression at ...
)The text was updated successfully, but these errors were encountered: