DSL scope control with @DslMarker in Kotlin - Time & Space Complexity

Time Complexity: DSL scope control with @DslMarker

O(n)

Understanding Time Complexity

When using Kotlin's DSL scope control with @DslMarker, it's important to understand how the program runs as the input grows.

We want to know how the number of operations changes when we build nested DSL structures.

Scenario Under Consideration

Analyze the time complexity of the following Kotlin DSL builder code.

@DslMarker
annotation class HtmlTagMarker

@HtmlTagMarker
class Html {
    private val children = mutableListOf()
    fun head(init: Head.() -> Unit) { children.add(Head().apply(init)) }
    fun body(init: Body.() -> Unit) { children.add(Body().apply(init)) }
}

@HtmlTagMarker
class Head {
    fun title(text: String) {}
}

@HtmlTagMarker
class Body {
    fun p(text: String) {}
}

fun html(init: Html.() -> Unit): Html = Html().apply(init)

This code defines a simple HTML DSL with scope control using @DslMarker to avoid confusion in nested blocks.

Identify Repeating Operations

Look for loops or repeated calls inside the DSL builders.

• Primary operation: Each nested block calls apply(init) which runs the lambda passed to it.
• How many times: The number of nested blocks determines how many times these lambdas run.

How Execution Grows With Input

As you add more nested tags inside the DSL, each block runs its lambda once.

Input Size (nested tags)	Approx. Operations
10	About 10 lambdas executed
100	About 100 lambdas executed
1000	About 1000 lambdas executed

Pattern observation: The work grows roughly in direct proportion to the number of nested blocks you create.

Final Time Complexity

Time Complexity: O(n)

This means the time to build the DSL grows linearly with the number of nested blocks.

Common Mistake

[X] Wrong: "Using @DslMarker adds extra loops or slows down the DSL building significantly."

[OK] Correct: @DslMarker only affects how the compiler checks scope, it does not add runtime loops or extra operations.

Interview Connect

Understanding how DSL scope control affects execution helps you write clear and efficient Kotlin DSLs, a useful skill in many Kotlin projects.

Self-Check

"What if we added recursion inside the DSL builders? How would the time complexity change?"

Practice

1. What is the main purpose of the @DslMarker annotation in Kotlin DSLs?

easy

A. To limit function visibility and prevent accidental calls to outer DSL scopes inside nested blocks.

B. To mark a function as deprecated in DSL usage.

C. To automatically generate DSL builder classes.

D. To enable inline functions in DSL builders.

Solution

1. Step 1: Understand DSL nesting problem

   In nested DSL blocks, functions from outer scopes can be accidentally called inside inner blocks, causing confusion.

2. Step 2: Role of @DslMarker

   @DslMarker annotation marks DSL builder classes to restrict visibility of outer scope functions inside nested DSL blocks, preventing accidental calls.

3. Final Answer:

   To limit function visibility and prevent accidental calls to outer DSL scopes inside nested blocks. -> Option A

4. Quick Check:

   @DslMarker controls scope visibility = A [OK]

Hint: Remember: @DslMarker hides outer DSL functions inside nested blocks [OK]

Common Mistakes:

• Thinking @DslMarker generates code automatically
• Confusing @DslMarker with deprecation annotations
• Assuming @DslMarker enables inline functions

2. Which of the following is the correct way to define a DSL marker annotation in Kotlin?

easy

A. fun @DslMarker MyDslMarker() {}"

B. annotation class DslMarker

C. @DslMarker fun MyDslMarker() {}

D. @DslMarker annotation class MyDslMarker

Solution

1. Step 1: Recall syntax for DSL marker annotation

   DSL marker annotations must be annotated with @DslMarker and declared as annotation classes.

2. Step 2: Identify correct syntax

   @DslMarker annotation class MyDslMarker correctly declares an annotation class with @DslMarker annotation: @DslMarker annotation class MyDslMarker.

3. Final Answer:

   @DslMarker annotation class MyDslMarker -> Option D

4. Quick Check:

   DSL marker annotation syntax = A [OK]

Hint: DSL marker annotations are annotation classes with @DslMarker prefix [OK]

Common Mistakes:

• Defining DSL marker as a function instead of annotation class
• Missing the @DslMarker annotation on the annotation class
• Using incorrect placement of @DslMarker keyword

3. Consider the following Kotlin DSL code snippet with two DSL marker annotations applied:

@DslMarker
annotation class FirstDsl

@DslMarker
annotation class SecondDsl

@FirstDsl
class BuilderA {
    fun a() = println("A")
    fun buildB(block: BuilderB.() -> Unit) {
        BuilderB().apply(block)
    }
}

@SecondDsl
class BuilderB {
    fun b() = println("B")
    fun buildA(block: BuilderA.() -> Unit) {
        BuilderA().apply(block)
    }
}

fun main() {
    BuilderA().apply {
        a()
        buildB {
            b()
            // Which call is allowed here?
            // a() or b() or both?
        }
    }
}

Which function call is allowed inside the buildB block?

medium

A. Only a() is allowed; b() is not visible.

B. Both a() and b() are allowed inside buildB block.

C. Only b() is allowed; a() is not visible due to DSL marker scope control.

D. Neither a() nor b() is allowed inside buildB block.

Solution

1. Step 1: Understand effect of multiple @DslMarker annotations

   Each DSL marker annotation restricts visibility of outer scope functions from classes annotated with different DSL markers.

2. Step 2: Analyze nested block visibility

   Inside buildB block (BuilderB scope), only b() is visible. The a() function from BuilderA is hidden due to different DSL markers.

3. Final Answer:

   Only b() is allowed; a() is not visible due to DSL marker scope control. -> Option C

4. Quick Check:

   Different DSL markers hide outer scope functions = C [OK]

Hint: Different DSL markers hide outer scope functions inside nested blocks [OK]

Common Mistakes:

• Assuming all functions from outer scopes are visible
• Ignoring effect of multiple DSL markers
• Confusing which DSL marker applies where

4. Given the following Kotlin DSL code, what is the error and how to fix it?

@DslMarker
annotation class MyDsl

@MyDsl
class Outer {
    fun outerFun() = println("Outer")
    fun inner(block: Inner.() -> Unit) {
        Inner().apply(block)
    }
}

@MyDsl
class Inner {
    fun innerFun() = println("Inner")
}

fun main() {
    Outer().apply {
        outerFun()
        inner {
            outerFun() // Error here
            innerFun()
        }
    }
}

medium

A. Error: innerFun() is not visible; fix by removing @MyDsl annotation.

B. Error: Cannot call outerFun() inside inner block due to DSL marker scope control; fix by qualifying with [e-mail]().

C. Error: inner block is not called; fix by changing Inner().block() to Inner().apply(block).

D. No error; code runs fine.

Solution

1. Step 1: Identify cause of error

   Inside the inner block, outerFun() is not directly visible because @MyDsl restricts access to outer scope functions.

2. Step 2: Fix by explicit qualification

   Use explicit label [e-mail]() to call the outer function inside the inner block, bypassing DSL marker restriction.

3. Final Answer:

   Error: Cannot call outerFun() inside inner block due to DSL marker scope control; fix by qualifying with [e-mail](). -> Option B

4. Quick Check:

   Use explicit this@Outer to access outer functions [OK]

Hint: Use this@Outer to call outer functions blocked by DSL marker [OK]

Common Mistakes:

• Removing @DslMarker annotation instead of qualifying call
• Ignoring the need for explicit receiver labels
• Assuming innerFun() visibility causes error

5. You want to create a Kotlin DSL for building HTML-like structures with nested tags. You define two builder classes HtmlBuilder and BodyBuilder, both annotated with the same @DslMarker annotation. How does using @DslMarker help prevent mistakes when writing nested DSL code like html { body { div { ... } } }?

hard

A. It prevents calling functions from HtmlBuilder inside BodyBuilder blocks unless explicitly qualified, avoiding accidental outer scope calls.

B. It automatically generates HTML tags for each builder class.

C. It allows calling any function from HtmlBuilder inside BodyBuilder without restrictions.

D. It disables nested DSL blocks to simplify code.

Solution

1. Step 1: Understand nested DSL structure

   In nested DSLs like HTML, inner blocks (BodyBuilder) are inside outer blocks (HtmlBuilder).

2. Step 2: Role of @DslMarker in nested builders

   @DslMarker annotation restricts visibility of outer builder functions inside inner builder blocks, preventing accidental calls to outer scope functions without explicit qualification.

3. Final Answer:

   It prevents calling functions from HtmlBuilder inside BodyBuilder blocks unless explicitly qualified, avoiding accidental outer scope calls. -> Option A

4. Quick Check:

   @DslMarker hides outer builder functions inside nested blocks [OK]

Hint: Use @DslMarker to avoid accidental outer scope calls in nested DSLs [OK]

Common Mistakes:

• Thinking @DslMarker generates code automatically
• Assuming all functions remain visible inside nested blocks
• Believing @DslMarker disables nesting