Named companion objects in Kotlin - Time & Space Complexity

Time Complexity: Named companion objects

O(n)

Understanding Time Complexity

Let's explore how the time it takes to run code with named companion objects changes as the program grows.

We want to see how the number of operations changes when using named companion objects in Kotlin.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

class Example {
    companion object Factory {
        fun createList(n: Int): List {
            val list = mutableListOf()
            for (i in 1..n) {
                list.add(i)
            }
            return list
        }
    }
}

fun main() {
    val numbers = Example.Factory.createList(1000)
}

This code defines a named companion object Factory inside a class Example. It creates a list of numbers from 1 to n.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop that adds numbers to the list.
• How many times: It runs exactly n times, once for each number from 1 to n.

How Execution Grows With Input

As n grows, the loop runs more times, so the work grows in a straight line with n.

Input Size (n)	Approx. Operations
10	10
100	100
1000	1000

Pattern observation: Doubling n doubles the work because each number is added once.

Final Time Complexity

Time Complexity: O(n)

This means the time to create the list grows directly with the number of items you want to add.

Common Mistake

[X] Wrong: "Using a named companion object makes the code slower because it adds extra steps."

[OK] Correct: The companion object is just a way to organize code. It does not add loops or repeated work, so it does not affect how the time grows with input size.

Interview Connect

Understanding how companion objects work and their impact on performance shows you know how Kotlin organizes code and how that relates to efficiency.

Self-Check

"What if the createList function used recursion instead of a loop? How would the time complexity change?"

Practice

1. What is the main purpose of naming a companion object in Kotlin?

easy

A. To give a clear and specific name to the singleton object inside a class

B. To create multiple instances of the companion object

C. To make the companion object inherit from another class

D. To prevent the companion object from being accessed outside the class

Solution

1. Step 1: Understand companion objects

   Companion objects are singletons inside a class used to hold members related to the class itself.

2. Step 2: Purpose of naming companion objects

   Giving a name to a companion object helps to clearly identify and access its members, improving code readability.

3. Final Answer:

   To give a clear and specific name to the singleton object inside a class -> Option A

4. Quick Check:

   Named companion object = clear singleton name [OK]

Hint: Named companion objects clarify singleton usage [OK]

Common Mistakes:

• Thinking companion objects create multiple instances
• Confusing naming with inheritance
• Assuming naming restricts access

2. Which of the following is the correct syntax to declare a named companion object in Kotlin?

easy

A. class MyClass { companionobject Named { fun greet() = "Hi" } }

B. class MyClass { companion Named object { fun greet() = "Hi" } }

C. class MyClass { companion object Named { fun greet() = "Hi" } }

D. class MyClass { object companion Named { fun greet() = "Hi" } }

Solution

1. Step 1: Recall correct companion object syntax

   The correct syntax is 'companion object Name { ... }' inside the class.

2. Step 2: Check each option

   class MyClass { companion object Named { fun greet() = "Hi" } } matches the correct syntax exactly. Others have misplaced keywords or wrong order.

3. Final Answer:

   class MyClass { companion object Named { fun greet() = "Hi" } } -> Option C

4. Quick Check:

   companion object Name { } syntax [OK]

Hint: Remember: 'companion object Name' order is fixed [OK]

Common Mistakes:

• Swapping 'object' and 'companion' keywords
• Writing 'companionobject' as one word
• Placing the name before 'companion'

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

class Box {
    companion object Factory {
        fun create() = "Box created"
    }
}
fun main() {
    println(Box.Factory.create())
}

medium

A. Factory created

B. Box created

C. Compilation error

D. Runtime exception

Solution

1. Step 1: Understand named companion object usage

   The companion object named 'Factory' holds the function 'create' which returns "Box created".

2. Step 2: Analyze the main function call

   Calling 'Box.Factory.create()' accesses the named companion object and calls 'create', printing "Box created".

3. Final Answer:

   Box created -> Option B

4. Quick Check:

   Box.Factory.create() prints "Box created" [OK]

Hint: Call named companion with ClassName.Name.method() [OK]

Common Mistakes:

• Trying to call create() without Factory prefix
• Expecting 'Factory created' output
• Confusing syntax causing compile errors

4. Identify the error in this Kotlin code snippet:

class Sample {
    companion object Companion {
        fun info() = "Info"
    }
}
fun main() {
    println(Sample.companion.info())
}

medium

A. Incorrect companion object name usage; should be 'Companion' not 'companion'

B. Missing 'object' keyword in companion declaration

C. Function 'info' must be static

D. No error; code runs fine

Solution

1. Step 1: Check companion object name and usage

   The companion object is named 'Companion' with uppercase C.

2. Step 2: Analyze the call in main()

   The code calls 'Sample.companion.info()' with lowercase 'companion', which does not match the name and causes a compile error.

3. Final Answer:

   Incorrect companion object name usage; should be 'Companion' not 'companion' -> Option A

4. Quick Check:

   Use exact companion object name when calling [OK]

Hint: Match companion object name exactly (case sensitive) [OK]

Common Mistakes:

• Using lowercase 'companion' instead of named object
• Forgetting 'object' keyword
• Assuming companion functions must be static

5. You want to create a Kotlin class Logger with a named companion object Factory that provides a method create() returning a new Logger instance. Which code correctly implements this?

hard

A. class Logger {
companion Factory object {
fun create() = Logger()
}
}

B. class Logger {
companion object {
fun create() = Logger()
}
}

C. class Logger {
object Factory companion {
fun create() = Logger()
}
}

D. class Logger {
companion object Factory {
fun create() = Logger()
}
}

Solution

1. Step 1: Recall correct syntax for named companion object

   The correct syntax is 'companion object Factory { ... }' inside the class.

2. Step 2: Check method implementation

   The method 'create()' returns a new instance of Logger using 'Logger()'. class Logger { companion object Factory { fun create() = Logger() } } matches both syntax and logic.

3. Final Answer:

   class Logger { companion object Factory { fun create() = Logger() } } -> Option D

4. Quick Check:

   Named companion object with factory method = class Logger { companion object Factory { fun create() = Logger() } } [OK]

Hint: Use 'companion object Name' and return new instance inside [OK]

Common Mistakes:

• Swapping 'object' and 'companion' keywords
• Omitting the companion object name
• Incorrect order of keywords