hey guys, scratching my head over

@JvmOverloads

on a data class constructor- it doesn’t seem that every permutation of the constructor is created to match default parameters

@JvmOverloads doesn’t create every permutation

attempting to provide a sane API for a java client when I have a data class like:

data class Foo @JvmOverloads constructor(bar: String, baz: Int, dimble: Int? = null, farb: Int? = 20)

And I’m getting a handful of constructors generated

It will just create overloads with -1 argument

JvmOverloads generate just the "tailing" overloads with default args.

yes, tailing is good word for this behavior

I believe it's

10!

🙂

Yeah, may be

creating manual overloads of the constructor it is then 👍 thanks guys

Also I found that builder function with some meaningful name is better choice for Java interop than secondary constructors which harder write and which pollute constructor completion for Kotlin