Today's Question:  What does your personal desk look like?        GIVE A SHOUT

Go channel explained

  sonic0002        2022-12-10 22:24:26       1,734        0    

In Go, a channel is a type of concurrent data structure that allows two or more goroutines (Go's term for lightweight threads) to communicate with each other. Channels provide a way for goroutines to send and receive values, and they are an essential part of Go's concurrency model.

Here's a simple example that demonstrates how to use channels in Go:

package main

import (
    "fmt"
)

func main() {
    // Create a new channel with the `make` function
    ch := make(chan int)

    // Start a new goroutine that sends the value 5 to the channel
    go func() {
        ch <- 5
    }()

    // Read the value from the channel using the `<-` operator
    fmt.Println(<-ch) // Output: 5
}

In this example, we create a new channel using the make function, and then we start a goroutine that sends the value 5 to the channel using the ch <- 5 expression. In the main goroutine, we read the value from the channel using the <- operator, which prints 5 to the console.

Channels can be buffered, meaning that they can hold a fixed number of values without a corresponding receiver for those values. Here's an example of using a buffered channel:

// Make a channel of strings buffering up to 2 values.
messages := make(chan string, 2)

// Because this channel is buffered, we can send these values into the channel
// without a corresponding concurrent receive.
messages <- "buffered"
messages <- "channel"

// Later we can receive these two values as usual.
fmt.Println(<-messages)
fmt.Println(<-messages)
An unbuffered channel means that the sender will only be able to send a value on the channel when there is a receiver ready to receive it. A buffered channel, on the other hand, can hold a certain number of values in a buffer before the sender is blocked. 

Channels can be used to synchronize the execution of goroutines. Here's an example of using a channel to block a goroutine until another goroutine has finished executing:

// This is the function we'll run in a goroutine. The done channel will be
// used to notify another goroutine that this function's work is done.
func worker(done chan bool) {
  fmt.Print("working...")
  time.Sleep(time.Second)
  fmt.Println("done")

  // Send a value to notify that we're done.
  done <- true
}

func main() {
  // Start a worker goroutine, giving it the channel to notify on.
  done := make(chan bool, 1)
  go worker(done)

  // Block until we receive a notification from the worker on the channel.
  <-done
}

In this example, the main goroutine is blocked until it receives a value from the done channel, which is sent by the worker goroutine when it has finished its work. This synchronization mechanism can be used to ensure that a program only terminates after all goroutines have finished their work.

Another powerful feature of channels is that they can be used to implement various concurrent data structures, such as concurrent queues and concurrent maps. This can be useful in situations where you need to share data between goroutines in a thread-safe manner.

For example, you can use a channel to implement a concurrent queue. Here is a simple implementation of a concurrent queue that uses a channel:

type Queue struct {
    // The channel used to store the queue items
    ch chan interface{}
}

// Enqueue adds an item to the queue
func (q *Queue) Enqueue(item interface{}) {
    // Send the item on the channel
    q.ch <- item
}

// Dequeue removes an item from the queue
func (q *Queue) Dequeue() interface{} {
    // Receive an item from the channel and return it
    return <-q.ch
}

In conclusion, channels are a powerful tool for concurrent programming in Go. They allow goroutines to communicate and synchronize with each other, and can be used to implement various concurrent data structures. Whether you are new to Go or an experienced developer, it is worth learning how to use channels effectively in your programs.

GOLANG  CHANNEL 

Share on Facebook  Share on Twitter  Share on Weibo  Share on Reddit 

  RELATED


  0 COMMENT


No comment for this article.