I am now already thinking for a longer time if I s...
# atrium
r
I am now already thinking for a longer time if I should remove overloads which contain
nullable
(I introduced them in 0.7.0) => see https://github.com/robstoll/atrium/issues/60 for further information. I introduced them for two reasons (taking
assert(listOf(1, 2, null)).containsNullableValues(1, null)
as example): 1. one cannot pass
null
to the non-nullable version 2. one sees immediately that one deals with a nullable element type I can resolve point 1 once Kotlin supports lower bounds (https://youtrack.jetbrains.com/issue/KT-209), I hope that does not take too long. My question is thus regarding the 2. point. What do you think, is such a hint: 1️⃣ valuable 2️⃣ confusing/makes things more complicated thanks for your participation
2️⃣ 1
1️⃣ 2