hey guys, scratching my head over `@JvmOverloads` ...

# announcements

[czuckie]

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

[gildor]

@JvmOverloads doesn’t create every permutation

[czuckie]

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

[czuckie]

which permutations does it generate? how can I get it to generate more? or how do I hand roll my own constructors?

[gildor]

It will just create overloads with -1 argument

[Kristoffer Andersen]

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

[gildor]

yes, tailing is good word for this behavior

[gildor]

If it would generate every permutations, for 10 arguments it would create how many, 1000 constructors?

[Kristoffer Andersen]

I believe it's 10! 🙂

[gildor]

Yeah, may be

[gildor]

anyway, it wouldn’t work, because it doesn’t work if params have the same type

[czuckie]

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

[gildor]

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