I don't like `repeat` when you actually use the index, it reads wrong to me. So I'd replace that wit...

# getting-started

[karelpeeters]

I don't like repeat when you actually use the index, it reads wrong to me. So I'd replace that with a for loop instead. I always like the StringBuilder / apply combo, so that's fine IMO.

[Shawn]

curious that there isn’t a buildString(String) { ... }

[Shawn]

there’s one that accepts an int and a lambda, but it just uses the int to set the initial capacity

[Hullaballoonatic]

i guess i could easily write one....

[karelpeeters]

Turns out there is a buildString with exactly this behavior! https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.text/build-string.html

[Hullaballoonatic]

oh my!

[karelpeeters]

Ah wait you were talking about the prefix part, my bad I completely misunderstood what you were saying.

[Shawn]

lmao no worries

[karelpeeters]

Actually now I'm even more confused, what would you want buildString(String) { ... } to do?

[Shawn]

StringBuilder(String) takes a string to initialize the builder - buildString could do the same

[karelpeeters]

Hmm I see.

[Hullaballoonatic]

is there any advantage to stringbuilder over just string arithmetic like +?

[Shawn]

mostly just the methods that the builder provides

[Shawn]

they’re pretty convenient and, being named, they can be more descriptive, depending on the the code it’s being used in

[Shawn]

if you’re building using a loop, then StringBuilder is a lot faster

[Shawn]

when you’re just adding strings together, the StringBuilder and the + approach are the same - the compiler will transform the latter into the former

[Shawn]

but the same optimization isn’t performed in a forEach or anything like that

[Shawn]

(at least, I’m pretty certain it’s not 😅)