Channel creation in Go - Time & Space Complexity

Time Complexity: Channel creation

O(1)

Understanding Time Complexity

When we create a channel in Go, we want to know how long it takes as the program runs.

We ask: Does making a channel take more time if the program is bigger or smaller?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

package main

func main() {
    ch := make(chan int)
    _ = ch
}

This code creates a new channel for integers and stores it in variable ch.

Identify Repeating Operations

Look for loops or repeated steps.

• Primary operation: Creating a single channel with make(chan int).
• How many times: Exactly once, no loops or repeats.

How Execution Grows With Input

Creating one channel takes the same time no matter what.

Input Size (n)	Approx. Operations
10	1
100	1
1000	1

Pattern observation: The time to create a channel stays the same even if the program or input size grows.

Final Time Complexity

Time Complexity: O(1)

This means creating a channel takes a fixed amount of time, no matter how big the program or input is.

Common Mistake

[X] Wrong: "Creating a channel takes longer if the program has more data or runs longer."

[OK] Correct: Creating a channel is a simple setup step that does not depend on data size or program length.

Interview Connect

Understanding that channel creation is quick and constant helps you explain how Go manages communication efficiently.

Self-Check

"What if we create multiple channels inside a loop? How would the time complexity change?"

Practice

1. What is the correct way to create an unbuffered channel of integers in Go?

easy

A. ch := chan int{}

B. ch := new(chan int)

C. ch := make(chan int)

D. ch := make(int chan)

Solution

1. Step 1: Understand channel creation syntax

   Channels are created using the built-in make function with the syntax make(chan Type).

2. Step 2: Identify the correct option

   ch := make(chan int) uses make(chan int), which is the correct syntax for an unbuffered integer channel.

3. Final Answer:

   ch := make(chan int) -> Option C

4. Quick Check:

   make(chan int) = correct channel creation [OK]

Hint: Use make(chan Type) to create channels in Go [OK]

Common Mistakes:

• Using new(chan int) instead of make
• Incorrect syntax like chan int{}
• Swapping order in make(int chan)

2. Which of the following creates a buffered channel of strings with capacity 5?

easy

A. ch := make(chan string, cap=5)

B. ch := make(chan string, 5)

C. ch := make(chan string, "5")

D. ch := make(chan string)

Solution

1. Step 1: Recall buffered channel syntax

   Buffered channels are created by passing a second argument to make, which is the capacity (an integer).

2. Step 2: Identify the correct option

   ch := make(chan string, 5) correctly uses make(chan string, 5) to create a buffered string channel with capacity 5.

3. Final Answer:

   ch := make(chan string, 5) -> Option B

4. Quick Check:

   make(chan string, 5) = buffered channel [OK]

Hint: Add capacity as second arg in make for buffered channels [OK]

Common Mistakes:

• Omitting capacity for buffered channel
• Using string instead of int for capacity
• Incorrect syntax with named parameters

3. What will be the output of this Go code?

ch := make(chan int, 2)
ch <- 10
ch <- 20
fmt.Println(<-ch)
fmt.Println(<-ch)

medium

A. 10
20

B. 20
10

C. 10
10

D. Compilation error

Solution

1. Step 1: Understand buffered channel behavior

   The channel has capacity 2, so it can hold two values without blocking. Values 10 and 20 are sent in order.

2. Step 2: Read values from channel in FIFO order

   Receiving from the channel returns values in the order sent: first 10, then 20.

3. Final Answer:

   10 20 -> Option A

4. Quick Check:

   Buffered channel FIFO order = 10 then 20 [OK]

Hint: Buffered channels output values in send order (FIFO) [OK]

Common Mistakes:

• Assuming output reverses order
• Expecting runtime or compile error
• Confusing buffered with unbuffered channel behavior

4. Identify the error in this Go code snippet:

ch := make(chan int)
ch <- 5
fmt.Println(<-ch)

medium

A. Deadlock: sending on unbuffered channel without receiver

B. Syntax error in channel creation

C. Cannot print channel value directly

D. No error, code runs fine

Solution

1. Step 1: Analyze unbuffered channel send

   Unbuffered channels block the sender until a receiver is ready. Here, send happens before receive.

2. Step 2: Identify deadlock situation

   Since no goroutine is receiving concurrently, the send blocks forever causing deadlock.

3. Final Answer:

   Deadlock: sending on unbuffered channel without receiver -> Option A

4. Quick Check:

   Unbuffered send blocks without receiver = deadlock [OK]

Hint: Unbuffered send blocks until receive happens [OK]

Common Mistakes:

• Thinking code compiles but runs fine
• Confusing syntax error with runtime deadlock
• Assuming print causes error

5. You want to create a channel that can hold up to 3 float64 values without blocking the sender immediately. Which code snippet correctly does this and sends three values safely?

hard

A. ch := make(chan float64, 3)
<-ch
<-ch
<-ch

B. ch := make(chan float64)
ch <- 1.1
ch <- 2.2
ch <- 3.3

C. ch := make(chan float64, 2)
ch <- 1.1
ch <- 2.2
ch <- 3.3

D. ch := make(chan float64, 3)
ch <- 1.1
ch <- 2.2
ch <- 3.3

Solution

1. Step 1: Create buffered channel with capacity 3

   Use make(chan float64, 3) to create a channel that can hold 3 float64 values without blocking.

2. Step 2: Send three values safely

   Sending three values to this buffered channel will not block because capacity matches the number of sends.

3. Final Answer:

   ch := make(chan float64, 3) ch <- 1.1 ch <- 2.2 ch <- 3.3 -> Option D

4. Quick Check:

   Buffered channel capacity 3 allows 3 sends without blocking [OK]

Hint: Buffer size must match or exceed sends to avoid blocking [OK]

Common Mistakes:

• Using unbuffered channel for multiple sends
• Buffer smaller than sends causing deadlock
• Receiving before sending without goroutine