Is it a kotlin bug if a non nullable class constru...

# multiplatform

[rebok]

Is it a kotlin bug if a non nullable class constructor parameter
is null at init {...}? If I make it wait for ex. 1 second with coroutines it works and the value is not null. The parameter is immutable.

[ephemient]

https://youtrack.jetbrains.com/issue/KT-10455

[ephemient]

there really isn't a solution without breaking compatibility with Java initialization though. at best some more cases could be warned about

[rebok]

The issue linked by you talks about uninitialized values by means of them being declared but not yet set. In my case it's a class constructor parameter.

[rebok]

Bump

[Jacob Ras]

Lol, don't bump so quickly

[Jacob Ras]

Do you have a bit of example code?

[rebok]

yes -> https://github.com/libki-kt/LOGik/blob/main/Core/src/commonMain/kotlin/org/duckdns/libki/LOGik/core/Logger.kt

[rebok]

bump

[CLOVIS]

Seriously, stop bumping everyone in the channel, you've already been warned. Bumping the thread is one thing, but everyone else doesn't need a notification.

[rebok]

ok, i will stop

[Jacob Ras]

Also; try to provide some more details. I looked at the file linked but don't know exactly what the issue is. Which line, which variable?

[rebok]

oh, i sent the wrong file, the right one is -> https://github.com/libki-kt/LOGik/blob/main/Behaviour/ConsoleLoggingBehaviour/src/[…]lin/org/duckdns/libki/LOGik/consoleLogger/BasicConsoleLogger.kt

class BasicConsoleLogger(
    val blockingRules: BlockingRulesConfigurationScope.() -> Unit = {}
) : Logger(<http://LogLevel.Info|LogLevel.Info>) { ... }

and the blockingRules constructor parameter