Why DSLs improve readability in Kotlin - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a simple DSL function that prints a greeting.

Kotlin

fun greet() {
    println([1])
}

greet()

Drag options to blanks, or click blank then click option'

Aprintln("Hello")

BHello, DSL!

C"Hello, DSL!"

Dgreet

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to put quotes around the greeting text.

Passing a function name instead of a string.

The println function needs a string argument, so the greeting must be in quotes.

2fill in blank

medium

Complete the code to create a DSL builder function that adds two numbers.

Kotlin

fun addNumbers(block: () -> Int): Int {
    return [1]()
}

val result = addNumbers { 5 + 3 }
println(result)

Drag options to blanks, or click blank then click option'

AaddNumbers

Bblock

Cprintln

Dresult

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to return the function name without calling it.

Using println instead of calling the block.

The block parameter is a function that returns an Int, so calling block() executes it.

3fill in blank

hard

Fix the error in the DSL function that builds a greeting message.

Kotlin

fun greeting(block: GreetingBuilder.() -> Unit): String {
    val builder = GreetingBuilder()
    builder.[1](block)
    return builder.message
}

class GreetingBuilder {
    var message = ""
    fun sayHello() {
        message = "Hello from DSL!"
    }
}

println(greeting { sayHello() })

Drag options to blanks, or click blank then click option'

Aapply

Brun

Cinvoke

Dcall

Attempts:

3 left

💡 Hint

Common Mistakes

Using run which returns the block result instead of the object.

Trying to call invoke or call which are not applicable here.

The apply function runs the block with the receiver and returns the receiver object.

4fill in blank

hard

Fill both blanks to create a DSL that builds a list of strings with a custom builder.

Kotlin

class StringListBuilder {
    val items = mutableListOf<String>()
    fun add(item: String) { items.[1](item) }
}

fun buildList(block: StringListBuilder.() -> Unit): List<String> {
    val builder = StringListBuilder()
    builder.[2](block)
    return builder.items
}

val list = buildList {
    add("apple")
    add("banana")
}
println(list)

Drag options to blanks, or click blank then click option'

Aadd

Bapply

Cremove

Drun

Attempts:

3 left

💡 Hint

Common Mistakes

Using remove instead of add to add items.

Using run instead of apply which returns the object.

The add function adds an item to the list, and apply runs the block on the builder object.

5fill in blank

hard

Fill all three blanks to create a DSL that builds a map with keys and values.

Kotlin

class MapBuilder {
    val map = mutableMapOf<String, Int>()
    fun put(key: String, value: Int) { map.[1](key, value) }
}

fun buildMap(block: MapBuilder.() -> Unit): Map<String, Int> {
    val builder = MapBuilder()
    builder.[2](block)
    return builder.[3]
}

val result = buildMap {
    put("one", 1)
    put("two", 2)
}
println(result)

Drag options to blanks, or click blank then click option'

Aput

Bapply

Cmap

Drun

Attempts:

3 left

💡 Hint

Common Mistakes

Using run instead of apply which returns the builder.

Returning the builder instead of the map property.

Using add instead of put for the map.

The put method adds entries to the map, apply runs the block on the builder, and map returns the built map.

Practice

1. Why do DSLs (Domain Specific Languages) improve code readability in Kotlin?

easy

A. They replace Kotlin with another programming language.

B. They require more complex syntax and keywords.

C. They make code longer and harder to follow.

D. They use clear, natural language-like syntax tailored for specific tasks.

Solution

1. Step 1: Understand DSL purpose

   DSLs are designed to use simple, natural language-like code for specific tasks.

2. Step 2: Compare readability effects

   This clear syntax makes code easier to read and understand compared to general-purpose code.

3. Final Answer:

   They use clear, natural language-like syntax tailored for specific tasks. -> Option D

4. Quick Check:

   DSLs improve readability by clear syntax = A [OK]

Hint: DSLs use natural language style code for clarity [OK]

Common Mistakes:

• Thinking DSLs make code more complex
• Confusing DSLs with general-purpose languages
• Assuming DSLs replace Kotlin entirely

2. Which Kotlin syntax feature helps create readable DSLs?

easy

A. Using semicolons after every statement

B. Declaring variables with var only

C. Using infix functions to write natural expressions

D. Avoiding lambdas in code

Solution

1. Step 1: Identify Kotlin features for DSLs

   Kotlin supports infix functions that allow calling functions without dots or parentheses, making code look natural.

2. Step 2: Evaluate options

   Semicolons are optional, var is unrelated, and lambdas are essential for DSLs, so only infix functions improve readability.

3. Final Answer:

   Using infix functions to write natural expressions -> Option C

4. Quick Check:

   Infix functions improve DSL readability = B [OK]

Hint: Infix functions make DSL code look natural [OK]

Common Mistakes:

• Thinking semicolons improve DSL readability
• Ignoring the role of lambdas in DSLs
• Confusing var declaration with DSL syntax

3. What is the output of this Kotlin DSL-like code?

fun buildString(block: StringBuilder.() -> Unit): String {
    val sb = StringBuilder()
    sb.block()
    return sb.toString()
}

val result = buildString {
    append("Hello")
    append(", ")
    append("DSL")
}
println(result)

medium

A. Hello, DSL

B. Hello DSL

C. Hello,DSL

D. Compilation error

Solution

1. Step 1: Understand buildString function

   It creates a StringBuilder, runs the block on it, then returns the built string.

2. Step 2: Trace the block calls

   The block appends "Hello", then ", ", then "DSL" to the StringBuilder, resulting in "Hello, DSL".

3. Final Answer:

   Hello, DSL -> Option A

4. Quick Check:

   Appended strings combined = "Hello, DSL" [OK]

Hint: Follow append calls to build final string [OK]

Common Mistakes:

• Ignoring the comma and space in append
• Assuming no spaces added automatically
• Thinking it causes a compilation error

4. Identify the error in this Kotlin DSL snippet:

fun html(block: HtmlBuilder.() -> Unit): String {
    val builder = HtmlBuilder()
    block(builder)
    return builder.toString()
}

class HtmlBuilder {
    fun body(content: String) {
        println("$content")
    }
}

html {
    body("Welcome")
}

medium

A. No error, code runs correctly

B. block(builder) should be builder.block()

C. html function should return Unit, not String

D. body function should return String instead of Unit

Solution

1. Step 1: Check how block is called

   block is a lambda with receiver HtmlBuilder, so it should be called as builder.block(), not block(builder).

2. Step 2: Understand Kotlin lambda with receiver call syntax

   Calling block(builder) passes builder as argument, but block expects receiver context, so this causes error.

3. Final Answer:

   block(builder) should be builder.block() -> Option B

4. Quick Check:

   Lambda with receiver called as receiver.lambda() = D [OK]

Hint: Call lambda with receiver as receiver.lambda() [OK]

Common Mistakes:

• Calling lambda with receiver like normal function
• Changing return types unnecessarily
• Assuming no error in calling block(builder)

5. How does Kotlin's DSL support help improve readability when building HTML-like structures? Choose the best explanation.

hard

A. By allowing nested lambdas with receivers to mimic HTML tags naturally

B. By forcing all HTML tags to be strings passed to functions

C. By requiring explicit string concatenation for every tag

D. By disallowing use of lambdas to keep code simple

Solution

1. Step 1: Understand Kotlin DSL features for HTML

   Kotlin allows nested lambdas with receivers, so you can write code that looks like nested HTML tags.

2. Step 2: Compare options

   Requiring explicit string concatenation or forcing tags as strings leads to less readable code, and disallowing lambdas is false because they are key to DSLs.

3. Final Answer:

   By allowing nested lambdas with receivers to mimic HTML tags naturally -> Option A

4. Quick Check:

   Nested lambdas mimic HTML = C [OK]

Hint: Nested lambdas mimic nested HTML tags [OK]

Common Mistakes:

• Thinking DSLs require string concatenation
• Believing lambdas are disallowed in DSLs
• Assuming DSLs use plain strings only