I have a api which takes varargs. Its basically a wrapper around String.format and there is a few la...

# getting-started

[ursus]

I have a api which takes varargs. Its basically a wrapper around String.format and there is a few layers to it.
From what I see in the bytecode, every function call forces me to use spread operator which creates a copy of the vararg string array.

Should I optimize this away and pass around only a Array<String>? feels very wasteful .. I mean we pass by reference on JVM
// Not to mention if I call kotlin format then there is another damn copy when it proxies to java
TLDR; are vararg apis harmful?

[ephemient]

if you're calling a vararg Kotlin function, you can avoid the copy by using the named parameter instead of a spread
if you're calling Java, https://youtrack.jetbrains.com/issue/KT-17043

[ursus]

hmm I still see the copying

fun initialize() {
    foo("meh", "yo")
}

fun foo(vararg args: String) {
    bar(args = args)
}

fun bar(vararg args: String) {
}

public final void initialize() {
  this.foo("meh", "yo");
}

public final void foo(@NotNull String... args) {
  Intrinsics.checkNotNullParameter(args, "args");
  this.bar((String[])Arrays.copyOf(args, args.length)); <---------------
}

public final void bar(@NotNull String... args) {
  Intrinsics.checkNotNullParameter(args, "args");
}

[ephemient]

that's surprising, and breaks my expectations; I've commented on the issue as such. I suppose there are no workarounds for the copy aside from reflection.

[ursus]

oh well, varargs are stupid