Why inheritance promotes code reuse in Blockchain / Solidity - Performance Analysis

Time Complexity: Why inheritance promotes code reuse

O(n)

Understanding Time Complexity

When using inheritance in blockchain smart contracts, we want to see how adding more inherited contracts affects the work the system does.

We ask: How does the execution time grow as we reuse more code through inheritance?

Scenario Under Consideration

Analyze the time complexity of the following Solidity code snippet.

contract Base {
    function baseFunction() public pure returns (uint) {
        return 1;
    }
}

contract Derived is Base {
    function derivedFunction() public pure returns (uint) {
        return baseFunction() + 1;
    }
}
    

This code shows a contract Derived inheriting from Base, reusing baseFunction inside its own function.

Identify Repeating Operations

Look for repeated actions that affect execution time.

• Primary operation: Calling baseFunction inside derivedFunction.
• How many times: Each call to derivedFunction calls baseFunction once.

How Execution Grows With Input

As you add more inherited functions and call them, the total work grows with how many functions run.

Input Size (number of inherited functions called)	Approx. Operations
1	1 function call
10	10 function calls
100	100 function calls

Pattern observation: The work grows linearly as you reuse more functions through inheritance.

Final Time Complexity

Time Complexity: O(n)

This means the execution time grows in a straight line with the number of inherited functions you call.

Common Mistake

[X] Wrong: "Inheritance makes the code run instantly with no extra cost."

[OK] Correct: Even though inheritance saves writing code again, each inherited function still runs when called, adding to execution time.

Interview Connect

Understanding how inheritance affects execution helps you write smart contracts that reuse code without surprises in performance.

Self-Check

What if we changed inherited functions to call each other recursively? How would the time complexity change?

Practice

1. Why does inheritance promote code reuse in blockchain smart contracts?

easy

A. It allows new contracts to use existing code without rewriting it

B. It makes contracts run faster on the blockchain

C. It encrypts the contract code automatically

D. It prevents contracts from being copied

Solution

1. Step 1: Understand inheritance concept

   Inheritance lets a new contract use code from an existing contract, avoiding rewriting.

2. Step 2: Identify how this saves effort

   By reusing code, developers save time and reduce errors, making maintenance easier.

3. Final Answer:

   It allows new contracts to use existing code without rewriting it -> Option A

4. Quick Check:

   Inheritance = reuse code [OK]

Hint: Inheritance means reuse existing code easily [OK]

Common Mistakes:

• Thinking inheritance speeds up contract execution
• Confusing inheritance with encryption
• Believing inheritance blocks code copying

2. Which of the following is the correct Solidity syntax to inherit from a contract named BaseContract?

easy

A. contract NewContract inherits BaseContract {}

B. contract NewContract from BaseContract {}

C. contract NewContract extends BaseContract {}

D. contract NewContract is BaseContract {}

Solution

1. Step 1: Recall Solidity inheritance syntax

   Solidity uses is keyword to inherit from another contract.

2. Step 2: Match syntax with options

   contract NewContract is BaseContract {} uses is correctly; others use invalid keywords.

3. Final Answer:

   contract NewContract is BaseContract {} -> Option D

4. Quick Check:

   Solidity inheritance uses 'is' [OK]

Hint: Remember Solidity uses 'is' for inheritance [OK]

Common Mistakes:

• Using 'inherits' or 'extends' instead of 'is'
• Forgetting curly braces after contract declaration
• Mixing syntax from other languages

3. Given the following Solidity code, what will be the output of getValue() when called on Child contract?

contract Parent {
    function getValue() public pure returns (string memory) {
        return "Parent";
    }
}

contract Child is Parent {
    function getValue() public pure returns (string memory) {
        return "Child";
    }
}

medium

A. "Parent"

B. "Child"

C. Compilation error due to duplicate function

D. Runtime error

Solution

1. Step 1: Understand function overriding in inheritance

   The Child contract overrides getValue() from Parent.

2. Step 2: Determine which function runs on Child

   Calling getValue() on Child runs the overridden version returning "Child".

3. Final Answer:

   "Child" -> Option B

4. Quick Check:

   Override method runs in child contract [OK]

Hint: Child overrides parent method, so child's version runs [OK]

Common Mistakes:

• Assuming parent method runs instead of child's
• Thinking duplicate functions cause compile error
• Confusing runtime errors with override behavior

4. Identify the error in this Solidity inheritance code:

contract A {
    uint public x = 5;
}

contract B is A {
    uint public x = 10;
}

medium

A. Variable x is redeclared in child contract causing shadowing

B. Missing constructor in child contract

C. Incorrect inheritance keyword used

D. No error, code is correct

Solution

1. Step 1: Check variable declarations in parent and child

   Both A and B declare x, causing shadowing.

2. Step 2: Understand shadowing issue

   Child's x hides parent's x, which can cause confusion or bugs.

3. Final Answer:

   Variable x is redeclared in child contract causing shadowing -> Option A

4. Quick Check:

   Variable redeclaration causes shadowing [OK]

Hint: Avoid redeclaring variables in child contracts [OK]

Common Mistakes:

• Ignoring variable shadowing effects
• Thinking constructors are mandatory for inheritance
• Confusing inheritance keyword syntax

5. You want to create a smart contract that reuses code from two existing contracts, Token and Ownable. Which approach best promotes code reuse and avoids duplication?

hard

A. Write new code that mimics Token and Ownable functions

B. Copy all code from Token and Ownable into the new contract

C. Create a new contract that inherits from both Token and Ownable

D. Deploy Token and Ownable separately and call them externally

Solution

1. Step 1: Understand multiple inheritance in Solidity

   Solidity supports inheriting from multiple contracts to reuse their code.

2. Step 2: Compare options for code reuse

   Inheriting from both Token and Ownable avoids duplication and keeps code organized.

3. Final Answer:

   Create a new contract that inherits from both Token and Ownable -> Option C

4. Quick Check:

   Multiple inheritance promotes reuse best [OK]

Hint: Use multiple inheritance to combine existing contracts [OK]

Common Mistakes:

• Copy-pasting code instead of inheriting
• Rewriting code manually causing errors
• Ignoring Solidity's multiple inheritance feature