Object creation and destruction flow in C++ - Time & Space Complexity

Time Complexity: Object creation and destruction flow

O(n)

Understanding Time Complexity

We want to understand how the time taken by a program changes when it creates and destroys objects.

How does the number of objects affect the total time spent on these actions?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

class MyClass {
public:
    MyClass() { /* constructor work */ }
    ~MyClass() { /* destructor work */ }
};

void createObjects(int n) {
    for (int i = 0; i < n; ++i) {
        MyClass obj;
    }
}
    

This code creates and destroys n objects one after another inside a loop.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Creating and destroying one object inside the loop.
• How many times: Exactly n times, once per loop iteration.

How Execution Grows With Input

Each object creation and destruction takes some fixed time. Doing this n times means the total time grows directly with n.

Input Size (n)	Approx. Operations
10	10 object creations + 10 destructions = 20 operations
100	100 creations + 100 destructions = 200 operations
1000	1000 creations + 1000 destructions = 2000 operations

Pattern observation: When n doubles, total operations roughly double too.

Final Time Complexity

Time Complexity: O(n)

This means the total time grows in a straight line as the number of objects increases.

Common Mistake

[X] Wrong: "Creating and destroying objects inside a loop is constant time because each object is small."

[OK] Correct: Even if each object is small, doing it many times adds up. The total time depends on how many objects you create and destroy.

Interview Connect

Understanding how object creation and destruction scale helps you reason about program speed and resource use in real projects.

Self-Check

What if we created objects dynamically with new inside the loop and deleted them after? How would the time complexity change?

Practice

1. Which of the following statements about object creation and destruction in C++ is correct?

easy

A. Constructors run only when an object is destroyed.

B. Destructors are called before an object is created.

C. Constructors are called automatically when an object is created.

D. Destructors run only when an object is created.

Solution

1. Step 1: Understand constructor timing

   Constructors are special functions that run automatically when an object is created to initialize it.

2. Step 2: Understand destructor timing

   Destructors run when an object is destroyed or goes out of scope, not before creation.

3. Final Answer:

   Constructors are called automatically when an object is created. -> Option C

4. Quick Check:

   Constructor = on creation [OK]

Hint: Remember: constructor = create, destructor = destroy [OK]

Common Mistakes:

• Confusing when constructors and destructors run
• Thinking destructors run before creation
• Believing constructors run on destruction

2. Which of the following is the correct syntax to declare a destructor for a class named Car in C++?

easy

A. ~Car();

B. Car();

C. void ~Car();

D. destructor Car();

Solution

1. Step 1: Recall destructor syntax

   In C++, a destructor is declared with a tilde (~) followed by the class name and parentheses, no return type.

2. Step 2: Check options

   ~Car(); matches the correct syntax: ~Car();. Others are invalid syntax.

3. Final Answer:

   ~Car(); -> Option A

4. Quick Check:

   Destructor syntax = ~ClassName() [OK]

Hint: Destructor always starts with ~ and no return type [OK]

Common Mistakes:

• Adding return type to destructor
• Using wrong keywords like 'destructor'
• Confusing constructor syntax with destructor

3. Consider the following C++ code:

class Test {
public:
  Test() { std::cout << "C"; }
  ~Test() { std::cout << "D"; }
};

int main() {
  Test t1;
  {
    Test t2;
  }
  std::cout << "E";
  return 0;
}

What is the output when this program runs?

medium

A. CCDEE

B. CCDED

C. CDEC

D. CCED

Solution

1. Step 1: Trace object creation

   t1 is created first, prints 'C'. Then t2 is created inside inner block, prints another 'C'.

2. Step 2: Trace object destruction and output

   When inner block ends, t2 is destroyed, prints 'D'. Then 'E' is printed. Finally, t1 is destroyed at program end, prints 'D'.

3. Final Answer:

   CCDED -> Option B

4. Quick Check:

   Creation C twice, destruction D twice, E in middle [OK]

Hint: Destructors run when objects go out of scope [OK]

Common Mistakes:

• Forgetting destructor runs at block end
• Mixing order of destruction
• Ignoring output inside main

4. Identify the error in the following C++ code snippet related to object destruction:

class Sample {
public:
  Sample() { std::cout << "Created"; }
  void ~Sample() { std::cout << "Destroyed"; }
};

int main() {
  Sample s;
  return 0;
}

medium

A. Destructor has a return type which is not allowed.

B. Destructor name is incorrect; it should be 'destruct'.

C. Constructor is missing a return type.

D. Destructor should be public static.

Solution

1. Step 1: Check destructor declaration

   Destructor must not have a return type. Here, 'void' before '~Sample()' is invalid syntax.

2. Step 2: Verify other options

   Destructor name is correct with '~Sample'. Constructors have no return type but that is correct here. Destructors cannot be static.

3. Final Answer:

   Destructor has a return type which is not allowed. -> Option A

4. Quick Check:

   Destructor = no return type [OK]

Hint: Destructor never has a return type, not even void [OK]

Common Mistakes:

• Adding void or other return types to destructor
• Misnaming destructor
• Making destructor static

5. You have a class Resource that opens a file in its constructor and closes it in its destructor. Which of the following code snippets correctly ensures the file is closed automatically when the object goes out of scope?

hard

A. void useFile() {
Resource* r = new Resource();
// use file
delete r;
} // file closed here automatically

B. void useFile() {
Resource* r = new Resource();
// use file
} // file closed here automatically

C. void useFile() {
Resource r;
// use file
delete &r;
} // file closed here

D. void useFile() {
Resource r;
// use file
} // file closed here automatically

Solution

1. Step 1: Understand automatic destruction

   Objects created on stack (like 'Resource r;') are destroyed automatically when going out of scope, calling destructor to close file.

2. Step 2: Analyze dynamic allocation

   Objects created with 'new' must be deleted manually; otherwise destructor won't run automatically, risking resource leaks.

3. Final Answer:

   void useFile() { Resource r; // use file } // file closed here automatically -> Option D

4. Quick Check:

   Stack objects auto-destroyed, heap objects need delete [OK]

Hint: Use stack objects for automatic destructor calls [OK]

Common Mistakes:

• Forgetting to delete heap objects
• Trying to delete stack objects
• Assuming destructor runs without delete on heap