robstoll
05/07/2018, 12:28 PMtoBe because you would quickly run into problems like asert(nullableVar).toBe(nonNullableVar) where you only see at runtime that the assert did not make sense. I think it is a good idea that the compiler can already give you a hint during writing your assertion code. But toBeNullable is a legit use case, if a user still passes a non-nullable value to this function, then it is on his behalf.