StringBuilder for performance in Kotlin - Step-by-Step Execution

Concept Flow - StringBuilder for performance

Create StringBuilder

↓

Append strings one by one

↓

StringBuilder holds combined string

↓

Call toString() to get final string

↓

Use final string

This flow shows how StringBuilder is created, strings are appended efficiently, and the final combined string is obtained.

Execution Sample

Kotlin

val sb = StringBuilder()
sb.append("Hello")
sb.append(", ")
sb.append("World!")
val result = sb.toString()
println(result)

This code builds a string "Hello, World!" step-by-step using StringBuilder for better performance.

Execution Table

Step	Action	StringBuilder Content	Result/Output
1	Create StringBuilder	""
2	Append "Hello"	"Hello"
3	Append ", "	"Hello, "
4	Append "World!"	"Hello, World!"
5	Call toString()	"Hello, World!"	Hello, World!
6	Print result	"Hello, World!"	Hello, World!

💡 All strings appended; final string printed; execution ends.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
sb (StringBuilder content)	""	"Hello"	"Hello, "	"Hello, World!"	"Hello, World!"	"Hello, World!"
result	null	null	null	null	"Hello, World!"	"Hello, World!"

Key Moments - 2 Insights

Why do we use StringBuilder instead of just adding strings with +?

Using + creates a new string each time, which is slow. StringBuilder changes one object, making it faster (see steps 2-4 in execution_table).

When do we get the final combined string from StringBuilder?

Only when we call toString() (step 5), the combined string is created for use or printing.

Visual Quiz - 3 Questions

Look at the execution_table, what is the content of StringBuilder after step 3?

A "Hello"

B "Hello, "

C "Hello, World!"

D ""

💡 Hint

Check the 'StringBuilder Content' column at step 3 in the execution_table.

At which step is the final string stored in variable 'result'?

A Step 2

B Step 4

C Step 5

D Step 6

💡 Hint

Look at the variable_tracker row for 'result' and see when it changes from null.

If we replaced StringBuilder with simple string concatenation (+), what would change in the execution_table?

A More steps creating new strings each append

B Fewer steps because + is faster

C No change in steps or content

D StringBuilder content would be empty

💡 Hint

Recall key_moments explanation about performance difference between + and StringBuilder.

Concept Snapshot

StringBuilder lets you build strings efficiently by appending pieces without creating new strings each time.
Create with StringBuilder(), append with append(), then get final string with toString().
Better performance than using + for many string joins.
Use when building strings in loops or many steps.

Full Transcript

This example shows how to use StringBuilder in Kotlin to build a string step-by-step. First, we create an empty StringBuilder. Then, we append "Hello", then ", ", then "World!". Each append adds to the same object, so it is fast. After all parts are added, we call toString() to get the final combined string "Hello, World!". Finally, we print the result. Using StringBuilder avoids creating many temporary strings, improving performance especially when joining many pieces.

Practice

1. What is the main advantage of using StringBuilder in Kotlin when combining many strings?

easy

A. It automatically sorts the strings alphabetically.

B. It stores strings in a database for later use.

C. It converts strings to uppercase by default.

D. It improves performance by reducing the number of string copies.

Solution

1. Step 1: Understand string concatenation cost

   Regular string concatenation creates new strings each time, which is slow.

2. Step 2: Role of StringBuilder

   StringBuilder appends strings without creating new copies each time, improving speed.

3. Final Answer:

   It improves performance by reducing the number of string copies. -> Option D

4. Quick Check:

   StringBuilder reduces copies [OK]

Hint: StringBuilder avoids repeated copying for faster string joining [OK]

Common Mistakes:

• Thinking StringBuilder sorts strings
• Assuming it changes string case automatically
• Believing it stores strings externally

2. Which of the following is the correct way to create a StringBuilder and add text in Kotlin?

easy

A. val sb = StringBuilder(); sb.add("Hello")

B. val sb = StringBuilder(); sb.append("Hello")

C. val sb = StringBuilder("Hello"); sb.add("World")

D. val sb = StringBuilder(); sb.insert("Hello")

Solution

1. Step 1: Check StringBuilder creation

   Creating with StringBuilder() is correct syntax.

2. Step 2: Identify correct method to add text

   The method to add text is append(), not add() or insert() with a string argument.

3. Final Answer:

   val sb = StringBuilder(); sb.append("Hello") -> Option B

4. Quick Check:

   Use append() to add text [OK]

Hint: Use append() method to add text to StringBuilder [OK]

Common Mistakes:

• Using add() instead of append()
• Using insert() incorrectly
• Passing strings to insert() without index

3. What will be the output of the following Kotlin code?

val sb = StringBuilder()
sb.append("Hi")
sb.append(", ")
sb.append("there!")
println(sb.toString())

medium

A. Hi, there!

B. Hi there!

C. Hi,there!

D. Hi, there

Solution

1. Step 1: Trace each append call

   First append adds "Hi", second adds ", ", third adds "there!".

2. Step 2: Combine all appended strings

   Combined string is "Hi, there!" exactly as appended.

3. Final Answer:

   Hi, there! -> Option A

4. Quick Check:

   Appended strings combined [OK]

Hint: Append strings in order, then call toString() [OK]

Common Mistakes:

• Missing spaces in appended strings
• Forgetting to call toString()
• Assuming append adds spaces automatically

4. Identify the error in the following Kotlin code using StringBuilder:

val sb = StringBuilder()
sb.append("Hello")
sb.append(123)
println(sb)

medium

A. Cannot append an integer directly to StringBuilder.

B. append() method requires two arguments.

C. There is no error in the code.

D. StringBuilder must be initialized with a string.

Solution

1. Step 1: Check append usage

   append can accept integers and converts them to string automatically, so no error here.

2. Step 2: Check printing StringBuilder directly

   Printing StringBuilder object directly calls its toString() method, so it prints the content correctly; no error here either.

3. Step 3: Re-examine options

   Actually, printing sb directly works fine in Kotlin, so no error. The code is correct.

4. Final Answer:

   No error; code runs and prints Hello123 -> Option C

5. Quick Check:

   Printing StringBuilder directly works [OK]

Hint: StringBuilder prints content directly without toString() [OK]

Common Mistakes:

• Thinking append can't take integers
• Assuming toString() is mandatory for printing
• Believing append needs two arguments

5. You want to build a comma-separated list of numbers from 1 to 5 using StringBuilder efficiently. Which code snippet correctly avoids adding an extra comma at the end?

hard

A. val sb = StringBuilder()
for (i in 1..5) {
sb.append(i)
if (i != 5) sb.append(",")
}
sb.toString()

B. val sb = StringBuilder()
for (i in 1..5) {
if (i > 0) sb.append(i).append(",") else sb.append(i)
}
sb.toString()

C. val sb = StringBuilder()
for (i in 1..5) {
sb.append(i).append(",")
}
sb.toString()

D. val sb = StringBuilder()
for (i in 1..5) {
sb.append(i)
sb.append(",")
}
sb.toString().removePrefix(",")

Solution

1. Step 1: Analyze each option for trailing comma

   val sb = StringBuilder() for (i in 1..5) { sb.append(i).append(",") } sb.toString() adds comma after every number, including last, causing extra comma.

2. Step 2: Check conditional comma addition

   val sb = StringBuilder() for (i in 1..5) { if (i > 0) sb.append(i).append(",") else sb.append(i) } sb.toString() tries to avoid comma on last number by if-else, but condition i > 0 is always true, so always appends comma after each number, causing trailing comma.

3. Step 3: Verify correct conditional append

   val sb = StringBuilder() for (i in 1..5) { sb.append(i) if (i != 5) sb.append(",") } sb.toString() appends number first, then adds comma only if not last number, correctly avoiding trailing comma.

4. Step 4: Check the remove prefix method

   val sb = StringBuilder() for (i in 1..5) { sb.append(i) sb.append(",") } sb.toString().removePrefix(",") appends comma always, then removes prefix "," from start (which doesn't exist), leaving trailing comma.

5. Final Answer:

   val sb = StringBuilder() for (i in 1..5) { sb.append(i) if (i != 5) sb.append(",") } sb.toString() -> Option A

6. Quick Check:

   Append comma only if not last [OK]

Hint: Add comma only if not last item in loop [OK]

Common Mistakes:

• Adding comma after every item including last
• Appending number twice in conditional branches
• Removing suffix after building string instead of conditional append