<Why does defining a nullable variable in a separa...

# stackoverflow

[rss]

Why does defining a nullable variable in a separate line change Kotlin compiler behavior?
// first piece of code start
var name1: String?
name1 = null
println(name1!!.length) // Unresolved reference: length
// first piece of code end

// second piece of code start
var name2: String? = null
println(name2!!.length)
// second piece of code end

When I hover my house over the "length" in the first piece of code, I get the message "Unresolved reference: length", and also "length" is in red. So, I figure out that the compiler already knows it is null and hence the message.
But doesn't...