StringBuilder for performance in Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is StringBuilder used for in Kotlin?

StringBuilder is used to efficiently build or modify strings without creating many temporary string objects.

beginner

Why is using StringBuilder better than using String concatenation in loops?

Because strings are immutable, concatenating them creates new objects each time. StringBuilder modifies the same object, improving speed and memory use.

beginner

How do you append text to a StringBuilder in Kotlin?

Use the append() method. For example: val sb = StringBuilder(); sb.append("Hello")

beginner

What method do you call to get the final string from a StringBuilder?

Use the toString() method to convert the StringBuilder content into a regular String.

intermediate

True or False: StringBuilder is thread-safe in Kotlin.

False. StringBuilder is not thread-safe. For thread-safe operations, use StringBuffer or other synchronization methods.

What happens when you concatenate strings repeatedly using + in Kotlin?

A Throws an error

B Modifies the original string directly

C Uses <code>StringBuilder</code> automatically for efficiency

D Creates many temporary string objects, slowing performance

Strings are immutable, so each concatenation creates a new string object, which can slow down performance.

Which method adds text to a StringBuilder?

A append()

B add()

C insert()

D concat()

The append() method adds text to the end of the StringBuilder.

How do you get the final string from a StringBuilder?

A build()

B toString()

C getString()

D convert()

Use toString() to convert the StringBuilder content into a regular string.

Is StringBuilder thread-safe?

A Only when synchronized manually

B Yes, always

C Only in Kotlin coroutines

D No, never

StringBuilder is not thread-safe by default. You must synchronize it manually for safe use in multiple threads.

Which of these is a benefit of using StringBuilder?

A Automatic memory management

B Immutable strings

C Faster string concatenation in loops

D Built-in thread safety

StringBuilder improves performance by avoiding many temporary string objects during concatenation.

Explain why StringBuilder improves performance when building strings in Kotlin.

Think about what happens when you add strings repeatedly.

Describe how to use StringBuilder to build a string from multiple parts.

Imagine writing a sentence word by word.

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