Andreas Sinz
05/28/2017, 4:09 PMKotlin has null safety
doesn't mean there are no `null`s anymore. IMHO it means that by mistake you won't get NPEs, You need something like !!
to produce NPEscedric
05/28/2017, 4:09 PM!!
. That's a very important property that very few languages offer today.ryotamurohoshi
05/28/2017, 4:18 PMryotamurohoshi
05/28/2017, 4:20 PMkevinmost
05/28/2017, 4:21 PM!!
. In practice, I've never seen a Kotlin codebase that fits these constraints though, which is why I'd love to see a compiler option to treat platform types as nullable typesryotamurohoshi
05/28/2017, 4:22 PMryotamurohoshi
05/28/2017, 4:23 PMryotamurohoshi
05/28/2017, 4:23 PMredrield
05/28/2017, 4:23 PMredrield
05/28/2017, 4:24 PMredrield
05/28/2017, 4:24 PMredrield
05/28/2017, 4:24 PMcedric
05/28/2017, 4:28 PMryotamurohoshi
05/28/2017, 4:35 PMryotamurohoshi
05/28/2017, 4:35 PMKotlin is null safety language
or Kotlin has null safety.
Because there is no clearly definition for null safety
in Kotlin document.
There are features description only.ryotamurohoshi
05/28/2017, 4:35 PMryotamurohoshi
05/28/2017, 4:36 PMsnrostov
05/28/2017, 4:38 PMclass C<T>{
x: T = null // ERROR: null cannot be assigned to non-null type T
}
snrostov
05/28/2017, 4:39 PMclass C<T>{
x: T? = null
}
grahamcox82
05/28/2017, 5:30 PMokkero
05/28/2017, 6:12 PMdeinspanjer
05/28/2017, 6:29 PMdeinspanjer
05/28/2017, 6:30 PMdeinspanjer
05/28/2017, 6:40 PMdeinspanjer
05/28/2017, 6:40 PMaaron_c
05/28/2017, 9:35 PMval list: ObservableList<Calendar> = things.map{ ObservableField(it)}
aaron_c
05/28/2017, 9:35 PMdiesieben07
05/28/2017, 9:36 PMkirillrakhman
05/28/2017, 9:36 PM