Was the feature to add @JvmOverloads to copy method was already asked? I am having issues with data ...

# random

[oshai]

Was the feature to add @JvmOverloads to copy method was already asked?
I am having issues with data class compatibility: https://github.com/jasync-sql/jasync-sql/issues/359

[ephemient]

data classes are challenging to evolve with API/ABI compatibility. the constructor also changes, as do componentN() destructuring

[ephemient]

https://jakewharton.com/public-api-challenges-in-kotlin/

[oshai]

yes... but constructor have jvm overloads and I only add new fields. I think only the copy is an issue in such case

[oshai]

Found this: https://stackoverflow.com/questions/52410264/is-it-possible-to-add-jvmoverloads-to-the-generated-copy-method-in-kotlin

[oshai]

and this: https://discuss.kotlinlang.org/t/jvmoverloads-for-data-classes/13659

[oshai]

but maybe I should open a new request for it?

[oshai]

I created a youtrack issue, you're welcome to vote: https://youtrack.jetbrains.com/issue/KT-56022/Support-JvmOverload-for-data-class-copy-function

[ephemient]

@JvmOverloads only addresses Java compatibility. Kotlin calls don't use the generated overloads so any change to the data class is binary incompatible for Kotlin (unless you write the overloads manually), whether you have @JvmOverloads or not.

[oshai]

For my original issue I change it to non data class and wrote the copy myself.

[ephemient]

my point is that @JvmOverloads constructor() and @JvmOverloads fun copy() still break binary compatibility for Kotlin callers when arguments are added, regardless of data class or not

[oshai]

that's unfortunate