no, it doesn't. Nothing to do with vararg, it seem...

# announcements

[horse_badorties]

no, it doesn't. Nothing to do with vararg, it seems.

fun foo(bool: Boolean = true, string1: String) {}
fun main(args: Array<String>) {
   foo("b") // does not compile
}

[karelpeeters]

Then that's probably how the rules of default parameters work. Doesn't look like there's an explanation on the site.

[hho]

yeah, it seems default values have to be "to the right" of given parameters (which makes sense, if you think that the types could be the same)

[horse_badorties]

but this doesn't compile as well:

fun foo(vararg strings: String, bool: Boolean = true) {}

fun main(args: Array<String>) {
    foo("a", "b", true) // does not compile
}

[karelpeeters]

Yea that never works, you can't have anything after varargs.

[horse_badorties]

so you can't mix vararg and default?

[karelpeeters]

Well you can if you put the defaults before the vararg.

[horse_badorties]

my bad, sorry

[horse_badorties]

foo("a", "b", bool = true) works, like documented

[karelpeeters]

I think they disallow normal parameters after vararg because typing wouldn't work that well.

[horse_badorties]

putting the default before the vararg was my initial example, @karelpeeters

[karelpeeters]

Yea I meant in the function definition, then you can use a default parameter without naming it at the callsite.

[horse_badorties]

like how?

[karelpeeters]

Ah my bad, that doesn't work either.