Why inheritance is class-only in Swift - Performance Analysis

Time Complexity: Why inheritance is class-only in Swift

O(1)

Understanding Time Complexity

We want to understand how the cost of using inheritance in Swift grows as programs get bigger.

Specifically, why inheritance works only with classes (not structs) and what that means for performance: constant-time dynamic dispatch.

Scenario Under Consideration

Analyze the time complexity of method calls in a class inheritance chain.

class Animal {
    func speak() {
        print("Animal sound")
    }
}

class Dog: Animal {
    override func speak() {
        print("Bark")
    }
}

let pet = Dog()
pet.speak()
    

This code shows a simple class inheritance where Dog inherits from Animal and overrides a method. Swift uses dynamic dispatch via vtables.

Identify Repeating Operations

Look at what happens when methods are called through inheritance.

• Primary operation: Dynamic method dispatch using the class's virtual method table (vtable).
• How many times: Once per method call; vtable lookup is constant time, independent of hierarchy depth.

How Execution Grows With Input

Method dispatch time does not grow with inheritance depth thanks to vtables.

Inheritance Depth (n)	Approx. Operations
1	1 vtable lookup
5	1 vtable lookup
10	1 vtable lookup

Pattern observation: The cost is constant (O(1)) regardless of the depth of the inheritance chain.

Final Time Complexity

Time Complexity: O(1)

This means the time to dispatch a method is constant, even as the inheritance chain gets longer.

Common Mistake

[X] Wrong: "Method dispatch in class inheritance walks the hierarchy linearly, taking O(n) time."

[OK] Correct: Swift classes use vtables for O(1) dynamic dispatch. Structs lack inheritance because they are value types without reference identity or dynamic dispatch, avoiding copying issues and enabling static dispatch via protocols.

Interview Connect

Explaining O(1) dispatch and why inheritance is class-only shows deep knowledge of Swift's type system, value vs. reference semantics, and performance trade-offs.

Self-Check

"Why can't structs inherit? How would adding dynamic dispatch to structs impact performance compared to classes?"

Practice

1. Why is inheritance only allowed for classes in Swift?

easy

A. Because only classes can have properties

B. Because structs and enums are faster to create

C. Because classes are reference types and share data by reference

D. Because structs and enums cannot have methods

Solution

1. Step 1: Understand type behavior in Swift

   Classes are reference types, meaning instances share the same data in memory.

2. Step 2: Compare with structs and enums

   Structs and enums are value types, so they copy data instead of sharing it.

3. Final Answer:

   Because classes are reference types and share data by reference -> Option C

4. Quick Check:

   Inheritance = Reference types only [OK]

Hint: Inheritance needs shared data, so only classes can do it [OK]

Common Mistakes:

• Thinking structs can inherit like classes
• Believing enums can have inheritance
• Confusing methods with inheritance

2. Which Swift declaration correctly shows inheritance allowed only for classes?

easy

A. class MyClass: ParentClass {}

B. struct MyStruct: ParentClass {}

C. enum MyEnum: ParentClass {}

D. protocol MyProtocol: ParentClass {}

Solution

1. Step 1: Identify inheritance syntax in Swift

   Only classes can inherit from other classes using the colon syntax.

2. Step 2: Check each declaration

   Structs, enums, and protocols cannot inherit from classes.

3. Final Answer:

   class MyClass: ParentClass {} -> Option A

4. Quick Check:

   Inheritance syntax = class only [OK]

Hint: Only classes use colon for inheritance from classes [OK]

Common Mistakes:

• Trying to inherit a class in a struct
• Using enum to inherit a class
• Confusing protocol inheritance with class inheritance

3. What will happen if you try this Swift code?

struct ParentStruct {}
struct ChildStruct: ParentStruct {}

medium

A. ChildStruct inherits ParentStruct successfully

B. Compile-time error: structs cannot inherit

C. Runtime error when creating ChildStruct

D. ChildStruct copies ParentStruct properties automatically

Solution

1. Step 1: Analyze struct inheritance rules

   Structs in Swift cannot inherit from other structs or classes.

2. Step 2: Predict compiler behavior

   The compiler will produce an error because inheritance is not allowed for structs.

3. Final Answer:

   Compile-time error: structs cannot inherit -> Option B

4. Quick Check:

   Struct inheritance = error [OK]

Hint: Structs cannot inherit; expect compile error [OK]

Common Mistakes:

• Assuming structs inherit like classes
• Expecting runtime error instead of compile error
• Thinking structs copy properties via inheritance

4. Find the error in this Swift code:

enum ParentEnum {}
class ChildClass: ParentEnum {}

medium

A. Enums cannot be inherited by classes

B. Enums cannot have child classes

C. Classes cannot inherit from enums

D. All of the above

Solution

1. Step 1: Check inheritance rules for enums and classes

   Enums are value types and cannot be inherited or used as base classes.

2. Step 2: Understand class inheritance restrictions

   Classes can only inherit from other classes, not enums.

3. Step 3: Combine observations

   All statements about enums and classes here are correct.

4. Final Answer:

   All of the above -> Option D

5. Quick Check:

   Enum inheritance = disallowed [OK]

Hint: Classes inherit classes only; enums can't be base classes [OK]

Common Mistakes:

• Thinking enums can be base classes
• Confusing enum cases with inheritance
• Ignoring that classes can't inherit enums

5. You want to share behavior between a struct and a class in Swift. Given inheritance is class-only, what is the best approach?

hard

A. Use a protocol to define shared behavior

B. Convert the struct to a class to inherit

C. Make the struct inherit from the class

D. Use enum inheritance to share code

Solution

1. Step 1: Recall inheritance limits

   Inheritance works only for classes, so structs cannot inherit from classes.

2. Step 2: Identify alternative sharing method

   Protocols allow both structs and classes to share behavior by conforming to them.

3. Step 3: Evaluate options

   Using protocols is the best way to share behavior without inheritance.

4. Final Answer:

   Use a protocol to define shared behavior -> Option A

5. Quick Check:

   Protocols share behavior across types [OK]

Hint: Use protocols to share behavior with structs and classes [OK]

Common Mistakes:

• Trying to inherit struct from class
• Converting structs unnecessarily to classes
• Thinking enums can inherit