Array Insertion at End in DSA C++ - Time & Space Complexity
We want to understand how long it takes to add a new item at the end of an array.
How does the time needed change as the array grows bigger?
Analyze the time complexity of the following code snippet.
void insertAtEnd(int arr[], int &size, int capacity, int value) {
if (size < capacity) {
arr[size] = value;
size++;
}
}
This code adds a new value at the end of an array if there is space.
Identify the loops, recursion, array traversals that repeat.
- Primary operation: One assignment to place the new value at the end.
- How many times: Exactly once per insertion.
Adding one item always takes the same small number of steps, no matter how big the array is.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | 1 assignment |
| 100 | 1 assignment |
| 1000 | 1 assignment |
Pattern observation: The time stays the same as the array grows.
Time Complexity: O(1)
This means adding an item at the end takes a constant amount of time regardless of array size.
[X] Wrong: "Adding at the end takes longer as the array grows because we have to move all elements."
[OK] Correct: We do not move existing elements when adding at the end; we just place the new item in the next free spot.
Knowing that adding at the end is fast helps you understand when arrays are a good choice and when other structures might be better.
"What if the array is full and we need to resize it before inserting? How would the time complexity change?"
Practice
Solution
Step 1: Understand fixed-size array behavior
Fixed-size arrays have a set size and cannot grow automatically.Step 2: Inserting at end when full
If the array is full, you cannot add a new element without overwriting or causing undefined behavior. If there is space available, the element is added at the next free position.Final Answer:
The element is added at the next free position if available -> Option CQuick Check:
Fixed-size array adds element only if space available [OK]
- Assuming array resizes automatically
- Thinking insertion always adds new space
- Expecting runtime error on insertion
Solution
Step 1: Recall vector insertion method
The standard method to add an element at the end of a vector is push_back.Step 2: Check syntax correctness
Only v.push_back(x); is valid C++ syntax for vector insertion at end.Final Answer:
v.push_back(x); -> Option BQuick Check:
Use push_back to insert at vector end [OK]
- Using non-existent methods like insert_end or add
- Confusing vector with other container methods
- Using append which is not a C++ vector method
int arr[5] = {1, 2, 3, 4, 5};
int n = 5;
int x = 10;
if (n < 5) {
arr[n] = x;
n++;
}
for (int i = 0; i < n; i++) {
std::cout << arr[i] << " ";
}Solution
Step 1: Check condition for insertion
The condition if (n < 5) is false because n equals 5, so insertion does not happen.Step 2: Print array elements
The loop prints all elements from index 0 to 4, which are 1 2 3 4 5.Final Answer:
1 2 3 4 5 -> Option DQuick Check:
Insertion skipped, original array printed [OK]
- Assuming insertion happens even if condition false
- Printing beyond array size
- Confusing array size with variable n
int arr[3] = {1, 2, 3};
int n = 3;
int x = 4;
arr[n] = x;
n++;
for (int i = 0; i < n; i++) {
std::cout << arr[i] << " ";
}Solution
Step 1: Check array size and insertion index
Array size is 3, valid indices are 0,1,2. Inserting at arr[3] is out of bounds.Step 2: Understand consequences of out-of-bounds access
Accessing arr[3] causes undefined behavior or runtime error.Final Answer:
Array index out of bounds when inserting element -> Option AQuick Check:
Insertion index must be within array size [OK]
- Ignoring array bounds when inserting
- Assuming array resizes automatically
- Incorrect loop boundary causing extra prints
Solution
Step 1: Check array capacity before insertion
Array size is 6, so insertion is safe only if n < 6.Step 2: Insert element and update count
If condition is true, assign arr[n] = 10 and increment n to reflect new size.Final Answer:
if (n < 6) { arr[n] = 10; n++; } -> Option AQuick Check:
Check capacity before insert, then add element [OK]
- Not checking array size before insertion
- Using <= instead of < causing overflow
- Wrong size limit in condition
Ready to prove it?
Pass the test and this pattern moves unknown
