π 1. Theory
π» 2. Code
π 3. Conclusion
The select statement
The select statement in Go looks like a switch
statement but forchannels
- Each case inside a select holds a channel receive or send.
- Select waits until one case is ready and then runs it and its associated case statement.
- It chooses one at random if multiple channels are ready.
- It will block until one of the channels is ready.
- I think the select statement is one of the most important part of the Go concurrency model.
Please let me know if you notice any mistakes or I forgot something important π
Show me the code
Let's code a classical program that's generate a Multiplication Table.
Take a look at the main function:
type message struct {
text string
number int
}
func main() {
msg := make(chan message)
exit := make(chan bool)
go readInput(msg, exit)
for {
select {
case m := <-msg:
validateInputAndGetNumber(&m)
printMultiplicationTable(m)
fmt.Print("Λ²Give me a number or exit: ")
case <-exit:
fmt.Println("Exiting program...")
os.Exit(1)
}
}
}
-
message struct
is the type of channel that I use to communicate between goroutines. There are just two goroutines in this program, the execution of main function and the execution of readInput function and yes, the main function is executed as a goroutine by go runtime. - Instantiate two channels:
msg
andexit
I hope the variable name is self-explanatoryπ . -
go readInput(msg, exit)
starts the goroutine to read the user input stdin data sending to the msg channel. -
for { select { ... } }
it starts an infinite loop with the for keyword. This way we can keep listening to both channels with select forever.
Therefore the goroutine executed by
go readInput(msg, exit)
is sending data through themsg
andexit
channels, and the goroutine executed bymain()
is reading these channels and then when one of the channels is ready, that operation will proceed, and its corresponding statements.
The running code seems like this:
Conclusion
My goal with this simple program is to demonstrate how we can use the select statement to handle incoming data from channels in a fancy way. I hope it could be helpful, especially for new Gophers π
Top comments (0)