Queue Concept and FIFO Principle in DSA Go - Time & Space Complexity

Time Complexity: Queue Concept and FIFO Principle

O(n) for dequeue, O(1) for enqueue

Understanding Time Complexity

We want to understand how the time to add or remove items from a queue changes as the queue grows.

How does the queue handle operations when it has more items?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

package main

import "fmt"

type Queue struct {
    items []int
}

func (q *Queue) Enqueue(val int) {
    q.items = append(q.items, val)
}

func (q *Queue) Dequeue() int {
    val := q.items[0]
    q.items = q.items[1:]
    return val
}

func main() {
    q := Queue{}
    q.Enqueue(1)
    q.Enqueue(2)
    fmt.Println(q.Dequeue())
    fmt.Println(q.Dequeue())
}
    

This code adds items to the end of the queue and removes items from the front, following FIFO.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Adding to the end and removing from the front of the slice.
• How many times: Each enqueue or dequeue runs once per call, but dequeue shifts the slice which can involve copying elements.

How Execution Grows With Input

As the queue grows, adding items stays quick, but removing items requires shifting remaining elements.

Input Size (n)	Approx. Operations for Dequeue
10	About 9 shifts
100	About 99 shifts
1000	About 999 shifts

Pattern observation: The number of shifts grows linearly with the queue size, making dequeue slower as the queue grows.

Final Time Complexity

Time Complexity: O(n) for dequeue, O(1) for enqueue

This means adding is fast and constant time, but removing takes longer as the queue grows because elements shift.

Common Mistake

[X] Wrong: "Both enqueue and dequeue always take constant time."

[OK] Correct: Removing from the front requires shifting all other elements, so it takes longer when the queue is bigger.

Interview Connect

Understanding how queue operations scale helps you explain trade-offs and choose the right data structure in real projects.

Self-Check

What if we used a linked list instead of a slice for the queue? How would the time complexity change?

Practice

1. What does the FIFO principle mean in the context of a queue?

easy

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

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

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

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

Solution

1. Step 1: Understand FIFO meaning

   FIFO means the first element that enters the queue is the first to leave.

2. Step 2: Match FIFO to queue behavior

   Queues follow FIFO, so the first added element is removed first.

3. Final Answer:

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

4. Quick Check:

   FIFO = First In, First Out [OK]

Hint: Remember queue = line; first come, first served [OK]

Common Mistakes:

• Confusing FIFO with LIFO
• Thinking last added is removed first
• Mixing stack behavior with queue

2. Which of the following is the correct way to declare a queue using a slice in Go?

easy

A. queue := []int{}

B. var queue []int

C. queue := make(map[int]int)

D. var queue int

Solution

1. Step 1: Identify slice declaration for queue

   In Go, a queue can be represented as a slice, initialized as empty with []int{}.

2. Step 2: Check options for correct slice syntax

   queue := []int{} uses slice literal syntax to create an empty int slice, suitable for queue.

3. Final Answer:

   queue := []int{} -> Option A

4. Quick Check:

   Slice queue declaration = queue := []int{} [OK]

Hint: Use slice literal []int{} for empty queue [OK]

Common Mistakes:

• Using map instead of slice
• Declaring queue as single int variable
• Using var without initialization for slice

3. What will be the output of the following Go code snippet?

package main
import "fmt"
func main() {
  queue := []int{10, 20, 30}
  // Dequeue operation
  first := queue[0]
  queue = queue[1:]
  fmt.Println(first)
  fmt.Println(queue)
}

medium

A. 10
[10 20 30]

B. 20
[10 30]

C. 10
[20 30]

D. 30
[10 20]

Solution

1. Step 1: Identify dequeue operation

   The first element 10 is stored in 'first', then queue is sliced from index 1 onward.

2. Step 2: Determine output values

   Printing 'first' outputs 10; printing 'queue' outputs remaining slice [20 30].

3. Final Answer:

   10 [20 30] -> Option C

4. Quick Check:

   Dequeue removes first element = 10, queue left = [20 30] [OK]

Hint: Dequeue removes first element, slice queue from index 1 [OK]

Common Mistakes:

• Printing old queue without slicing
• Confusing index positions
• Assuming queue unchanged after dequeue

4. Identify the error in the following Go code that tries to enqueue an element to a queue represented by a slice:

package main
func main() {
  queue := []int{1, 2, 3}
  queue[3] = 4
}

medium

A. Compile error because queue is not declared

B. Syntax error due to missing import statement

C. No error; element 4 is added correctly

D. Index out of range error because slice index 3 does not exist

Solution

1. Step 1: Analyze slice indexing

   Slice 'queue' has length 3 with indices 0,1,2; index 3 is out of range.

2. Step 2: Understand how to add elements

   To add elements, use append(queue, 4) instead of direct index assignment.

3. Final Answer:

   Index out of range error because slice index 3 does not exist -> Option D

4. Quick Check:

   Accessing queue[3] invalid for length 3 slice [OK]

Hint: Use append to add elements, not direct index assignment [OK]

Common Mistakes:

• Trying to assign beyond slice length
• Forgetting to use append for enqueue
• Assuming slice auto-expands on index assignment

5. Given a queue implemented as a slice in Go, how would you write a function to enqueue multiple elements at once while preserving FIFO order? Choose the correct code snippet.

func enqueueMultiple(queue []int, elements []int) []int {
  // Fill in
}

hard

A. return append(queue, elements...)

B. return append(elements, queue...)

C. for _, e := range elements { queue = append([]int{e}, queue...) } return queue

D. queue = elements; return queue

Solution

1. Step 1: Understand enqueue multiple elements

   To add multiple elements preserving order, append all new elements at the end of queue.

2. Step 2: Check code options for correct append usage

   return append(queue, elements...) uses append(queue, elements...) which adds all elements at the end in order.

3. Final Answer:

   return append(queue, elements...) -> Option A

4. Quick Check:

   Appending elements at end preserves FIFO enqueue order [OK]

Hint: Use append(queue, elements...) to add multiple items [OK]

Common Mistakes:

• Appending new elements before queue (wrong order)
• Replacing queue instead of appending
• Appending elements one by one at front