Is there an annotation to tell the compiler that expected field declaration should be a property on ...

# multiplatform

[Big Chungus]

Is there an annotation to tell the compiler that expected field declaration should be a property on JVM?

expect class File(path:String) {
  val path: String // <-- Needs to be property on jvm
}

// jvmMain
actual typealias File = java.io.File // <-- hooks in to `private String path` field instead of `public String getPath()` getter

[turansky]

Reversed JvmField?

[Big Chungus]

Pretty much

[Big Chungus]

Unfortunately there's no

@JvmUnoReverse
@JvmField
val property: Any

[turansky]

open modifier?

[turansky]

explicit get /`set` ?

[Big Chungus]

Tried those already. No dice 😕

[russhwolf]

It might work as an extension

expect class File(path: String)
expect val File.path: String

actual typealias File = java.io.File
actual val File.path get() = getPath()

[Big Chungus]

It does, but sadly we still don't have inline extension vals

[russhwolf]

Alternatively, you could use okio’s filesystem support or compare to what they do. They base everything around their own Path abstraction instead of typaliasing File

[Big Chungus]

Wasn't aware of that, will certainly have a look, thanks.