Virtual and override keywords in Blockchain / Solidity

Introduction

Virtual and override keywords help control how functions behave when you change or extend code. They let you change parts of a program safely without breaking it.

When you want to change how a function works in a new version of a contract.

When you build a contract that other contracts will extend and customize.

When you want to make sure the right function runs depending on the contract used.

When you want to avoid mistakes by clearly showing which functions can be changed.

When you want to keep your code organized and easy to update.

Syntax

Blockchain / Solidity

contract Base {
    function example() public virtual {
        // base code
    }
}

contract Child is Base {
    function example() public override {
        // new code
    }
}

virtual means the function can be changed in child contracts.

override means the function is changing a virtual function from a parent contract.

Examples

This function can be changed by contracts that inherit Animal.

Blockchain / Solidity

contract Animal {
    function sound() public virtual returns (string memory) {
        return "Some sound";
    }
}

This function changes the sound() function from Animal to return "Bark".

Blockchain / Solidity

contract Dog is Animal {
    function sound() public override returns (string memory) {
        return "Bark";
    }
}

Another example of overriding sound() to return "Meow".

Blockchain / Solidity

contract Cat is Animal {
    function sound() public override returns (string memory) {
        return "Meow";
    }
}

Sample Program

This program shows a base contract Vehicle with a virtual function move(). Two contracts, Car and Bike, override move() to give their own messages. The Test contract calls both to show the different results.

Blockchain / Solidity

pragma solidity ^0.8.0;

contract Vehicle {
    function move() public virtual returns (string memory) {
        return "Vehicle is moving";
    }
}

contract Car is Vehicle {
    function move() public override returns (string memory) {
        return "Car is driving";
    }
}

contract Bike is Vehicle {
    function move() public override returns (string memory) {
        return "Bike is pedaling";
    }
}

contract Test {
    function testMove() public pure returns (string memory, string memory) {
        Car car = new Car();
        Bike bike = new Bike();
        return (car.move(), bike.move());
    }
}

Important Notes

Always mark functions as virtual in the base contract if you want child contracts to change them.

When overriding, you must use the override keyword to avoid mistakes.

If you forget virtual or override, the compiler will give an error to help you fix it.

Summary

virtual lets a function be changed in child contracts.

override shows a function is changing a virtual function from a parent.

Using these keywords helps keep your blockchain contracts safe and easy to update.

Practice

1. What does the virtual keyword do in a blockchain smart contract?

easy

A. Makes a function private

B. Prevents a function from being changed

C. Deletes a function from the contract

D. Allows a function to be changed in child contracts

Solution

1. Step 1: Understand the role of virtual

   The virtual keyword marks a function so child contracts can change it.

2. Step 2: Compare with other options

   Options B, C, and D describe behaviors that virtual does not do.

3. Final Answer:

   Allows a function to be changed in child contracts -> Option D

4. Quick Check:

   virtual = allows override [OK]

Hint: Virtual means function can be changed later [OK]

Common Mistakes:

• Thinking virtual makes function private
• Confusing virtual with override
• Believing virtual deletes functions

2. Which of the following is the correct way to override a virtual function named transfer in a child contract?

easy

A. function transfer() public virtual { }

B. function transfer() public override { }

C. function transfer() public final { }

D. function transfer() public abstract { }

Solution

1. Step 1: Identify override syntax

   To replace a virtual function, use override keyword in the child function.

2. Step 2: Check options

   function transfer() public override { } uses override, correct for overriding. function transfer() public virtual { } uses virtual which allows override but does not override itself. Options C and D are incorrect keywords here.

3. Final Answer:

   function transfer() public override { } -> Option B

4. Quick Check:

   Override keyword replaces virtual function [OK]

Hint: Use override keyword to replace virtual function [OK]

Common Mistakes:

• Using virtual instead of override to replace function
• Using final or abstract incorrectly
• Omitting override keyword

3. Consider this Solidity code snippet:

contract Parent {
    function greet() public virtual returns (string memory) {
        return "Hello from Parent";
    }
}

contract Child is Parent {
    function greet() public override returns (string memory) {
        return "Hello from Child";
    }
}

contract Test {
    function testGreet() public returns (string memory) {
        Child c = new Child();
        return c.greet();
    }
}

What will testGreet() return when called?

medium

A. "Hello from Parent"

B. Compilation error

C. "Hello from Child"

D. Runtime error

Solution

1. Step 1: Understand virtual and override behavior

   The greet function in Parent is marked virtual, allowing Child to override it.

2. Step 2: Check which function is called

   When c.greet() is called on a Child instance, the overridden greet in Child runs, returning "Hello from Child".

3. Final Answer:

   "Hello from Child" -> Option C

4. Quick Check:

   Override function runs on child instance [OK]

Hint: Child override runs, not parent virtual function [OK]

Common Mistakes:

• Expecting parent function output
• Thinking override causes error
• Confusing virtual with abstract

4. What is wrong with this Solidity code?

contract Base {
    function foo() public virtual returns (string memory) {
        return "Base";
    }
}

contract Derived is Base {
    function foo() public returns (string memory) {
        return "Derived";
    }
}

medium

A. Missing override keyword in Derived's foo function

B. Base's foo function should not be virtual

C. Derived's foo function should be private

D. No errors, code is correct

Solution

1. Step 1: Check override rules

   Since foo in Base is virtual, the overriding function in Derived must use override keyword.

2. Step 2: Identify missing keyword

   The foo function in Derived lacks override, causing a compilation error.

3. Final Answer:

   Missing override keyword in Derived's foo function -> Option A

4. Quick Check:

   Override keyword required when replacing virtual function [OK]

Hint: Override keyword is mandatory when replacing virtual functions [OK]

Common Mistakes:

• Forgetting override keyword
• Thinking virtual is optional in base
• Making function private incorrectly

5. You have a contract hierarchy:

contract A {
    function calc() public virtual returns (uint) {
        return 1;
    }
}

contract B is A {
    function calc() public virtual override returns (uint) {
        return 2;
    }
}

contract C is B {
    function calc() public override returns (uint) {
        return 3;
    }
}

If you call calc() on a C contract instance, what is the output and why?

hard

A. 3, because C overrides B's function

B. 1, because A's function is virtual

C. 2, because B overrides A and is virtual

D. Compilation error due to multiple overrides

Solution

1. Step 1: Trace overrides in inheritance

   Contract A defines calc as virtual. B overrides it and keeps it virtual. C overrides B's version without virtual.

2. Step 2: Determine which function runs on C instance

   Calling calc() on C runs C's override, returning 3.

3. Final Answer:

   3, because C overrides B's function -> Option A

4. Quick Check:

   Most derived override runs on instance [OK]

Hint: Most derived override runs, even if base is virtual [OK]

Common Mistakes:

• Thinking base virtual function runs
• Confusing virtual with override
• Expecting compilation error from multiple overrides