Why result builders enable DSLs in Swift - Challenge Your Understanding

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Swift result builder example?

Consider this Swift code using a result builder to create a simple HTML DSL. What will be printed when running this code?

Swift

import Foundation

@resultBuilder
struct HTMLBuilder {
    static func buildBlock(_ components: String...) -> String {
        components.joined(separator: "\n")
    }
}

func html(@HTMLBuilder content: () -> String) -> String {
    "<html>\n" + content() + "\n</html>"
}

let page = html {
    "<head><title>Test</title></head>"
    "<body><h1>Hello, DSL!</h1></body>"
}

print(page)

A

<html>
<head><title>Test</title></head><body><h1>Hello, DSL!</h1></body>
</html>

B <html><head><title>Test</title></head><body><h1>Hello, DSL!</h1></body></html>

C Compilation error: Missing return in function

D

<html>
<head><title>Test</title></head>
<body><h1>Hello, DSL!</h1></body>
</html>

💡 Hint

Look at how the buildBlock joins components with new lines and how the html function wraps the content.

The result builder collects the strings and joins them with new lines. The html function adds tags with new lines around the content, so the output preserves line breaks.

🧠 Conceptual

intermediate

Why do result builders simplify DSL creation in Swift?

Which of the following best explains why result builders enable easy creation of DSLs in Swift?

A They replace all functions with macros at compile time.

B They enforce strict type checking preventing any implicit conversions.

C They allow writing nested code blocks that automatically combine results without explicit function calls.

D They require manual string concatenation for every DSL element.

💡 Hint

Think about how result builders let you write code that looks like natural language or markup.

Result builders let you write nested blocks that the compiler transforms into combined results, making DSLs look clean and readable.

🔧 Debug

advanced

Identify the error in this Swift result builder code

This Swift code using a result builder fails to compile. What is the cause?

Swift

@resultBuilder
struct ListBuilder {
    static func buildBlock(_ components: [String]...) -> [String] {
        components.flatMap { $0 }
    }
}

func list(@ListBuilder content: () -> [String]) -> [String] {
    content()
}

let items = list {
    ["Apple", "Banana"]
    ["Cherry"]
}

print(items)

A Error: Function 'list' missing @escaping attribute

B Error: Cannot convert value of type '[String]' to expected argument type 'String' in buildBlock

C Error: Missing return statement in buildBlock

D No error, prints ["Apple", "Banana", "Cherry"]

💡 Hint

Check the parameter types in buildBlock and what the closure returns.

The buildBlock expects parameters of type String but receives [String], causing a type mismatch error.

❓ Predict Output

advanced

What is the output of this Swift result builder with conditional logic?

Given this Swift code using a result builder with an if statement, what will be printed?

Swift

@resultBuilder
struct TextBuilder {
    static func buildBlock(_ components: String...) -> String {
        components.joined(separator: " ")
    }
    static func buildEither(first component: String) -> String {
        component
    }
    static func buildEither(second component: String) -> String {
        component
    }
}

func text(@TextBuilder content: () -> String) -> String {
    content()
}

let isMorning = true

let greeting = text {
    "Good"
    if isMorning {
        "morning"
    } else {
        "evening"
    }
    "everyone!"
}

print(greeting)

A Good morning everyone!

B Good evening everyone!

C

Good
morning
everyone!

D Compilation error: Missing buildEither methods

💡 Hint

Look at how buildEither handles the if-else and how buildBlock joins strings.

The if condition is true, so buildEither(first:) returns "morning". The buildBlock joins all strings with spaces, producing "Good morning everyone!".

🧠 Conceptual

expert

How do result builders improve code readability in DSLs?

Which statement best describes how result builders improve readability when creating DSLs in Swift?

A They let developers write nested, declarative code that looks like the target language, hiding boilerplate and combining results automatically.

B They force all DSL code to be written as flat functions without nesting, improving clarity.

C They require explicit calls to combine each DSL element, making the code verbose but clear.

D They convert all DSL code into JSON at compile time for better readability.

💡 Hint

Think about how DSLs look like natural language or markup with result builders.

Result builders allow writing nested blocks that resemble the DSL's structure, hiding complexity and improving readability.

Practice

1. What is the main reason result builders enable Domain Specific Languages (DSLs) in Swift?

easy

A. They replace all Swift syntax with a new language.

B. They automatically optimize code for faster execution.

C. They enforce strict type checking at compile time.

D. They allow combining multiple code statements into a single, readable result.

Solution

1. Step 1: Understand what result builders do

   Result builders combine multiple code pieces into one result, making code easier to read.

2. Step 2: Connect to DSL creation

   This combining ability lets developers write mini languages (DSLs) inside Swift that look clean and simple.

3. Final Answer:

   They allow combining multiple code statements into a single, readable result. -> Option D

4. Quick Check:

   Result builders combine code = C [OK]

Hint: Result builders combine code pieces into one result [OK]

Common Mistakes:

• Thinking result builders change Swift syntax completely
• Confusing result builders with performance optimizers
• Believing result builders only check types

2. Which of the following is the correct syntax to declare a result builder in Swift?

easy

A. @resultBuilder struct MyBuilder { ... }

B. resultBuilder MyBuilder { ... }

C. @resultBuilder func MyBuilder() { ... }

D. builderResult MyBuilder { ... }

Solution

1. Step 1: Recall result builder declaration syntax

   In Swift, result builders are declared using the attribute @resultBuilder before a struct or class.

2. Step 2: Match options with correct syntax

   @resultBuilder struct MyBuilder { ... } uses @resultBuilder before struct, which is correct syntax.

3. Final Answer:

   @resultBuilder struct MyBuilder { ... } -> Option A

4. Quick Check:

   @resultBuilder + struct = A [OK]

Hint: Result builders use @resultBuilder before struct [OK]

Common Mistakes:

• Using @resultBuilder on functions instead of structs
• Writing resultBuilder instead of @resultBuilder
• Mixing keywords builderResult or resultBuilder incorrectly

3. Given this Swift code using a result builder, what will be printed?

 @resultBuilder
struct SimpleBuilder {
    static func buildBlock(_ components: String...) -> String {
        components.joined(separator: ", ")
    }
}

func makeList(@SimpleBuilder content: () -> String) -> String {
    "List: " + content()
}

let result = makeList {
    "Apple"
    "Banana"
    "Cherry"
}
print(result)

medium

A. Apple, Banana, Cherry

B. List: Apple Banana Cherry

C. List: Apple, Banana, Cherry

D. List: ["Apple", "Banana", "Cherry"]

Solution

1. Step 1: Understand buildBlock behavior

   The buildBlock function joins all string components with ", ". So the strings "Apple", "Banana", "Cherry" become "Apple, Banana, Cherry".

2. Step 2: Analyze makeList output

   makeList prepends "List: " to the joined string, so the final output is "List: Apple, Banana, Cherry".

3. Final Answer:

   List: Apple, Banana, Cherry -> Option C

4. Quick Check:

   Joined strings with commas + prefix = A [OK]

Hint: Look for join separator in buildBlock to find output format [OK]

Common Mistakes:

• Ignoring the join separator and printing without commas
• Forgetting the "List: " prefix
• Assuming output is an array instead of a string

4. Identify the error in this Swift result builder code:

 @resultBuilder
struct NumberBuilder {
    static func buildBlock(_ components: Int...) -> Int {
        components.reduce(0, +)
    }
}

func makeSum(@NumberBuilder content: () -> Int) -> Int {
    content()
}

let total = makeSum {
    1
    "2"
    3
}
print(total)

medium

A. Function makeSum should not have a parameter.

B. Cannot mix Int and String in result builder components.

C. Result builder must return an array, not Int.

D. Missing return statement in buildBlock function.

Solution

1. Step 1: Check types in result builder components

   The buildBlock expects Int components, but the closure includes a String "2" which is invalid.

2. Step 2: Understand type mismatch error

   Mixing Int and String causes a compile-time error because the builder cannot combine different types.

3. Final Answer:

   Cannot mix Int and String in result builder components. -> Option B

4. Quick Check:

   Type mismatch in components = D [OK]

Hint: Check all builder inputs have the same type [OK]

Common Mistakes:

• Ignoring type mismatch between Int and String
• Thinking missing return causes error here
• Assuming result builder must return array

5. How can result builders be used to create a simple HTML DSL in Swift? Choose the best approach.

hard

A. Define a result builder that combines HTML element strings and use it to build nested HTML code.

B. Use result builders to automatically convert Swift structs into HTML tags without any code.

C. Result builders replace the need for HTML by generating Swift UI views only.

D. Result builders only work with numbers and cannot handle string-based DSLs like HTML.

Solution

1. Step 1: Understand result builders for DSLs

   Result builders let you combine multiple pieces of code into one result, perfect for building nested structures like HTML strings.

2. Step 2: Apply to HTML DSL creation

   By defining a result builder that joins HTML element strings, you can write clean Swift code that looks like HTML markup.

3. Final Answer:

   Define a result builder that combines HTML element strings and use it to build nested HTML code. -> Option A

4. Quick Check:

   Result builders combine strings for DSL = B [OK]

Hint: Use result builders to combine nested strings for DSLs [OK]

Common Mistakes:

• Thinking result builders auto-convert structs to HTML
• Believing result builders replace HTML completely
• Assuming result builders only work with numbers