Stack Concept and LIFO Principle in DSA C - Time & Space Complexity

Time Complexity: Stack Concept and LIFO Principle

O(1)

Understanding Time Complexity

We want to understand how long it takes to add or remove items from a stack.

How does the time change when the stack grows bigger?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Push operation: add item to stack
void push(int stack[], int *top, int value) {
    stack[++(*top)] = value;
}

// Pop operation: remove item from stack
int pop(int stack[], int *top) {
    return stack[(*top)--];
}
    

This code adds or removes one item from the top of the stack using the LIFO rule.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Single step to add or remove one item.
• How many times: Each push or pop does this once, no loops involved.

How Execution Grows With Input

Each push or pop takes the same short time no matter how big the stack is.

Input Size (n)	Approx. Operations
10	1 operation per push or pop
100	1 operation per push or pop
1000	1 operation per push or pop

Pattern observation: Time stays the same no matter how many items are in the stack.

Final Time Complexity

Time Complexity: O(1)

This means adding or removing an item takes a fixed, quick step regardless of stack size.

Common Mistake

[X] Wrong: "Pushing or popping takes longer as the stack grows because it has more items."

[OK] Correct: Each push or pop only changes the top item, so time does not grow with stack size.

Interview Connect

Knowing that stack operations are quick and constant time helps you explain efficient data handling in many programs.

Self-Check

"What if we had to search for an item inside the stack before popping? How would the time complexity change?"

Practice

1. What does the LIFO principle mean in the context of a stack?

easy

A. First In, First Out - the first element added is removed first

B. Last In, First Out - the last element added is removed first

C. Last In, First Out - the first element added is removed first

D. First In, Last Out - the first element added is removed last

Solution

1. Step 1: Understand LIFO meaning

   LIFO means the last element added to the stack is the first one to be removed.

2. Step 2: Match with options

   Last In, First Out - the last element added is removed first correctly describes this behavior as "Last In, First Out".

3. Final Answer:

   Last In, First Out - the last element added is removed first -> Option B

4. Quick Check:

   LIFO = Last In, First Out [OK]

Hint: Remember stack removes newest item first [OK]

Common Mistakes:

• Confusing LIFO with FIFO
• Thinking first added is removed first
• Mixing up order of insertion and removal

2. Which of the following is the correct way to push an element 'x' onto a stack named 's' in C?

easy

A. s.push = x;

B. s.push(x);

C. push(x, s);

D. push(s, x);

Solution

1. Step 1: Identify correct function call syntax in C

   In C, stack operations are usually functions like push(stack, element).

2. Step 2: Check options

   push(s, x); uses push(s, x); which is the correct syntax for pushing x onto stack s.

3. Final Answer:

   push(s, x); -> Option D

4. Quick Check:

   Function call push(stack, element) = push(s, x) [OK]

Hint: In C, function calls have parameters in parentheses [OK]

Common Mistakes:

• Using object.method() syntax (not C style)
• Swapping parameter order
• Assigning instead of calling function

3. Consider the following C code using a stack with push and pop operations:

push(s, 10);
push(s, 20);
pop(s);
push(s, 30);
pop(s);

What is the value returned by the last pop operation?

medium

A. 30

B. 20

C. 10

D. Error - stack empty

Solution

1. Step 1: Trace stack after each operation

   After push 10: stack = [10]
   After push 20: stack = [10, 20]
   pop(): removes 20, stack = [10]
   push 30: stack = [10, 30]
   pop(): removes 30

2. Step 2: Identify last pop value

   The last pop removes 30, so it returns 30.

3. Final Answer:

   30 -> Option A

4. Quick Check:

   Last pop returns last pushed element 30 [OK]

Hint: Last pushed is first popped, track stack top [OK]

Common Mistakes:

• Assuming FIFO order
• Forgetting previous pop removed top
• Mixing values pushed and popped

4. The following C code snippet is intended to pop an element from a stack 's'. What is the error?

int pop(Stack *s) {
    if (s->top == -1) {
        return -1;
    }
    return s->items[s->top++];
}

medium

A. The function returns -1 on empty stack

B. The stack pointer is not checked for NULL

C. The top index is incremented instead of decremented

D. The return type should be void

Solution

1. Step 1: Analyze pop operation logic

   Pop should return the top element and then decrease the top index.

2. Step 2: Identify error in index update

   Code uses s->top++ which increases top, wrong for pop. It should be s->top-- to remove top element.

3. Final Answer:

   The top index is incremented instead of decremented -> Option C

4. Quick Check:

   Pop decreases top index, not increases [OK]

Hint: Pop must decrease top index after returning element [OK]

Common Mistakes:

• Using post-increment instead of decrement
• Ignoring empty stack check
• Wrong return type for pop

5. You have a stack initially empty. You perform these operations:

push(s, 5);
push(s, 10);
pop(s);
push(s, 15);
push(s, 20);
pop(s);
pop(s);

What is the final state of the stack (from top to bottom)?

hard

A. 5

B. 10 -> 5

C. 15 -> 5

D. Empty stack

Solution

1. Step 1: Trace stack after each operation

   push 5: stack = [5]
   push 10: stack = [5, 10]
   pop: removes 10, stack = [5]
   push 15: stack = [5, 15]
   push 20: stack = [5, 15, 20]
   pop: removes 20, stack = [5, 15]
   pop: removes 15, stack = [5]

2. Step 2: Determine final stack state

   After all operations, stack has only 5 left at bottom and top.

3. Final Answer:

   5 -> Option A

4. Quick Check:

   Only 5 remains after pops [OK]

Hint: Track pushes and pops carefully to find final stack [OK]

Common Mistakes:

• Forgetting to remove top on pop
• Mixing order of elements
• Assuming stack is empty after pops