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

Time Complexity: Stack Concept and LIFO Principle

O(1)

Understanding Time Complexity

We want to understand how the time to do stack operations changes as the number of items grows.

How long does it take to add or remove items from a stack?

Scenario Under Consideration

Analyze the time complexity of the following stack operations.

class Stack:
    def __init__(self):
        self.items = []

    def push(self, item):
        self.items.append(item)

    def pop(self):
        return self.items.pop() if self.items else None

This code adds (push) and removes (pop) items following the last-in, first-out rule.

Identify Repeating Operations

Look at what repeats when we add or remove items.

• Primary operation: Adding or removing one item at the end of the list.
• How many times: Each push or pop does this once per call.

How Execution Grows With Input

Each push or pop takes about the same time no matter how many items are in the stack.

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

Pattern observation: The time stays about the same no matter how big the stack is.

Final Time Complexity

Time Complexity: O(1)

This means adding or removing an item takes a constant amount of time, no matter the stack size.

Common Mistake

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

[OK] Correct: The operations only touch the top item, so the rest of the stack size does not affect the time.

Interview Connect

Knowing that stack operations are quick and constant time helps you explain why stacks are useful for tasks like undo features or expression evaluation.

Self-Check

"What if we used a linked list instead of a list for the stack? How would the time complexity of push and pop change?"

Practice

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

easy

A. Last In, First Out - the first item added is the first to be removed

B. Last In, First Out - the last item added is the first to be removed

C. First In, First Out - the first item added is the first to be removed

D. First In, Last Out - the first item added is the last to be removed

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 item added is the first to be removed correctly describes this behavior as "Last In, First Out".

3. Final Answer:

   Last In, First Out - the last item added is the first to be removed -> 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 order of insertion and removal

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

easy

A. stack.append(5)

B. stack.add(5)

C. stack.push(5)

D. stack.insert(5)

Solution

1. Step 1: Recall Python list methods for stack

   Python uses list's append() method to add elements to the top of the stack.

2. Step 2: Check options for correct method

   Only stack.append(5) uses append(5), which is correct for pushing onto a stack.

3. Final Answer:

   stack.append(5) -> Option A

4. Quick Check:

   Push in Python stack = append() [OK]

Hint: Use append() to push in Python stack [OK]

Common Mistakes:

• Using push() which is not a Python list method
• Using add() which is for sets
• Using insert() which inserts at specific index

3. What will be the output of the following Python code?

stack = []
stack.append(10)
stack.append(20)
stack.append(30)
print(stack.pop())
print(stack.pop())
print(stack)

medium

A. 30
10
[20]

B. 10
20
[30]

C. 20
30
[10]

D. 30
20
[10]

Solution

1. Step 1: Trace stack after each append

   After append(10): [10], append(20): [10, 20], append(30): [10, 20, 30]

2. Step 2: Trace pop operations

   pop() removes last element: first pop() returns 30, second pop() returns 20, stack left is [10]

3. Final Answer:

   30 20 [10] -> Option D

4. Quick Check:

   Stack pops last in first out [OK]

Hint: Pop removes last pushed element first [OK]

Common Mistakes:

• Thinking pop removes first element
• Confusing order of popped elements
• Not updating stack after pop

4. Identify the error in the following code that implements a stack using a Python list:

stack = []
stack.push(1)
stack.push(2)
print(stack.pop())

medium

A. Using push() method which does not exist for Python lists

B. Using pop() method incorrectly

C. Stack should be initialized as a tuple, not list

D. Missing import statement for stack

Solution

1. Step 1: Check methods used on list

   Python lists do not have a push() method; append() is used to add elements.

2. Step 2: Verify pop() usage

   pop() is valid for lists and correctly used here.

3. Final Answer:

   Using push() method which does not exist for Python lists -> Option A

4. Quick Check:

   Python list push() does not exist [OK]

Hint: Use append(), not push(), to add in Python list [OK]

Common Mistakes:

• Assuming push() is valid for Python lists
• Thinking pop() needs arguments
• Confusing list with stack module

5. Given a stack implemented as a Python list, which sequence of operations will reverse the order of elements in the stack?
Assume initial stack is [1, 2, 3] where 3 is the top.
Choose the correct sequence:

hard

A. Append elements to the stack again without popping

B. Use pop() repeatedly and append to the same stack without extra storage

C. Pop all elements into a new stack

D. Sort the stack list in ascending order

Solution

1. Step 1: Understand reversing stack by popping

   Pop elements from original stack and push them into a new stack reverses order.

2. Step 2: Confirm other options

   Appending without popping or sorting does not reverse stack order correctly.

3. Final Answer:

   Pop all elements into a new stack -> Option C

4. Quick Check:

   Two stacks pop/push reverses order [OK]

Hint: Use two stacks to reverse order [OK]

Common Mistakes:

• Trying to reverse by sorting
• Appending without popping
• Using one stack without extra storage