Any type as universal base in Kotlin - Time & Space Complexity

Time Complexity: Any type as universal base

O(n)

Understanding Time Complexity

When using Kotlin's Any type as a universal base, it's important to see how operations on these objects grow with input size.

We want to know how the program's work changes as we handle more Any objects.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

fun printAll(items: List) {
    for (item in items) {
        println(item.toString())
    }
}

This code prints the string form of each item in a list of Any objects.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each item in the list.
• How many times: Once for every item in the list.

How Execution Grows With Input

As the list gets bigger, the program prints more items, so the work grows steadily.

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

Pattern observation: The work grows directly with the number of items.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows in a straight line as the list gets bigger.

Common Mistake

[X] Wrong: "Using Any makes the code slower because it has to check types for every item."

[OK] Correct: The loop runs once per item regardless of type. The toString() call is a simple method call and does not add extra loops or checks that change the overall time growth.

Interview Connect

Understanding how operations on universal types like Any scale helps you explain performance clearly and confidently in interviews.

Self-Check

"What if we changed the list to a nested list of Any objects? How would the time complexity change?"

Practice

1. In Kotlin, which type is the universal base type that can hold any kind of value?

easy

A. Universal

B. Object

C. Base

D. Any

Solution

1. Step 1: Understand Kotlin's type hierarchy

   Kotlin uses Any as the root of its type system, similar to Object in Java.

2. Step 2: Identify the universal base type

   Any can hold any non-null value, making it the universal base type in Kotlin.

3. Final Answer:

   Any -> Option D

4. Quick Check:

   Universal base type = Any [OK]

Hint: Remember: Kotlin's root type is called Any [OK]

Common Mistakes:

• Confusing Any with Object (Java's base type)
• Thinking Base or Universal are Kotlin types
• Assuming Any can hold null (it cannot)

2. Which of the following is the correct way to declare a variable of type Any in Kotlin?

easy

A. val x: Any = 10

B. val x = Any(10)

C. val x: Any() = 10

D. val x: any = 10

Solution

1. Step 1: Review Kotlin variable declaration syntax

   Variables are declared with val or var, followed by a colon and the type.

2. Step 2: Check correct usage of Any type

   Any is a type, not a constructor, so you assign values directly without parentheses.

3. Final Answer:

   val x: Any = 10 -> Option A

4. Quick Check:

   Declare with colon and type name = val x: Any = 10 [OK]

Hint: Use colon for type, no parentheses for Any [OK]

Common Mistakes:

• Trying to call Any as a constructor
• Using lowercase 'any' instead of 'Any'
• Adding parentheses after type name

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

fun main() {
    val a: Any = "Hello"
    val b: Any = 123
    println(a)
    println(b)
}

medium

A. Hello
123

B. Any
Any

C. Compilation error

D. null
null

Solution

1. Step 1: Understand variable assignments

   Variable a holds a string "Hello" and b holds an integer 123, both typed as Any.

2. Step 2: Analyze the print statements

   Printing a and b calls their toString() method, outputting "Hello" and "123" respectively.

3. Final Answer:

   Hello 123 -> Option A

4. Quick Check:

   Any holds values, prints their string form [OK]

Hint: Any prints actual value's string, not type name [OK]

Common Mistakes:

• Expecting type name 'Any' to print
• Thinking it causes compile error
• Assuming null prints for Any

4. Identify the error in this Kotlin code snippet:

fun main() {
    val x: Any = null
    println(x)
}

medium

A. Missing semicolon after println

B. println cannot print Any type

C. Cannot assign null to a variable of type Any

D. Variable x must be declared as var, not val

Solution

1. Step 1: Check type nullability

   Any in Kotlin is non-nullable by default, so it cannot hold null.

2. Step 2: Identify assignment error

   Assigning null to x of type Any causes a compile-time error.

3. Final Answer:

   Cannot assign null to a variable of type Any -> Option C

4. Quick Check:

   Any is non-nullable, null assignment fails [OK]

Hint: Any disallows null; use Any? for nullable [OK]

Common Mistakes:

• Thinking println can't print Any
• Expecting semicolons in Kotlin
• Confusing val and var for nullability

5. Given a list of mixed types, how can you create a new list containing only the string representations of elements using Any as the base type?

val mixedList: List<Any> = listOf(1, "two", 3.0, true)

Which Kotlin code correctly produces List<String> with string forms of all elements?

hard

A. val stringList = mixedList.filterIsInstance<String>()

B. val stringList = mixedList.map { it.toString() }

C. val stringList = mixedList.map { it as String }

D. val stringList = mixedList.filter { it is String }

Solution

1. Step 1: Understand the goal

   We want a list of strings representing all elements, not just the strings themselves.

2. Step 2: Analyze each option

   val stringList = mixedList.map { it.toString() } maps each element to its string form, producing List<String>. val stringList = mixedList.filterIsInstance<String>() filters only strings, losing other elements. val stringList = mixedList.map { it as String } tries unsafe cast causing runtime error. val stringList = mixedList.filter { it is String } filters strings but returns List<Any>, not List<String>.

3. Final Answer:

   val stringList = mixedList.map { it.toString() } -> Option B

4. Quick Check:

   Map all to string form for List<String> [OK]

Hint: Use map with toString() to convert all elements [OK]

Common Mistakes:

• Using filterIsInstance<String> loses non-string elements
• Casting with 'as String' causes runtime errors
• Filtering returns List<Any>, not List<String>