When would you use Select Statement Basics in a real project

The timeout pattern:

ch := make(chan string)
go func() {
    time.Sleep(200 * time.Millisecond)
    ch <- "slow result"
}()

select {
case result := <-ch:
    fmt.Println("got:", result)
case <-time.After(50 * time.Millisecond):
    fmt.Println("timeout")    // this fired (50ms < 200ms) — executed
}

The mechanics: time.After(d) returns a channel that receives one value after d. It's a case — the timer races with the other channels; whoever is ready first runs.

The per-operation timeout (idle detection) vs the TOTAL deadline:

// idle: each loop gets a FRESH 2s window
for {
    select {
    case item := <-work: process(item)
    case <-time.After(2 * time.Second): return  // idle timeout
    }
}

// total: ONE deadline across all iterations
timer := time.NewTimer(10 * time.Second)
for {
    select {
    case item := <-work: process(item)
    case <-timer.C: return  // total deadline
    }
}

The resource subtlety: time.After creates a timer that isn't stopped when another case wins — it sits in the runtime's timer heap until it fires. For most timeouts, negligible. For high-frequency selects with short timers, use time.NewTimer + timer.Stop() on the win path.