A modern programming language that makes developers happier.

kotlinlang

<https://blog.shreyaspatil.dev/runtime-surprise-kotlin-breaks-non-nullability-promise-on-developer-cheating-in-field-initialization>

yes there is a whole set of issues around initialization, <https://youtrack.jetbrains.com/issues?q=tag:%20use-before-initialization|https://youtrack.jetbrains.com/issues?q=tag:%20use-before-initialization>

It's not Kotlin specific, you can get same error in plain Java.

```public class Example
{
    Boolean value1 = computeValue1();
    String value2 = getData();
    Boolean computeValue1() {
        return value2.isEmpty();
    }
    static String getData() {
        return "SomeData";
    }
    public static void main(String[] args) {
        new Example();
    }
}```

In java, null-safety is not there. So it’s natural in Java

But let’s say in kotlin
```val something: Type```
`something` is val declared as Non nullable type, so it becomes tricky to identify such issues in code review or debugging.