Hello, World! I'm having trouble finding the correct syntax to declare an `expect` class and reflect...

# multiplatform

[bod]

Hello, World! I'm having trouble finding the correct syntax to declare an expect class and reflecting the constructors of the actual one. Here's what I'm trying to do:

common:

expect class File(path: String) {
    constructor(path: File, name: String)

    fun isDirectory(): Boolean
}

jvm:

actual class File actual constructor(path: String): java.io.File(path) {
    actual constructor(path: File, name: String)
}

This results in Primary constructor call expected

[sikri]

in kotlin you have to call primary constructor in your secondary
for jvm, secondary constructor is not calling primary, resulting in an error

[Kroppeb]

^

[bod]

but the secondary constructor exists in JVM, what's the proper syntax to just "export" it?

[sikri]

but it does not exist in Kotlin

[Kroppeb]

Could you cange the primary to a secondary?

[sikri]

I doubt that this way you will store semantics

[sikri]

path: File, name: String

may not be equal to
path.absolutePath + File.SEPARATOR + name

[sikri]

tbh I would look on

companion object {
    operator fun invoke(path: String)
    operator fun invoke(path: File, name: String)
}

but I don’t know if it is possible to have expect/actual companion object

[bod]

should I just do a wrapper

[sikri]

you can just copy logic of <http://java.io|java.io>.File constructor

[bod]

this seems to work

expect class File {
    constructor(path: String)
    constructor(path: File, name: String)

    fun isDirectory(): Boolean
}

actual class File : java.io.File {
    actual constructor(path: String):super(path)
    actual constructor(path: File, name: String):super(path, name)
}

[bod]

wait I think all I wanted was: actual typealias File = <http://java.io|java.io>.File 😂

[bod]

sorry for the noise/confusion

[Dico]

Primary constructor is not mandatory.