/explore
|
You are here 
|
aarol.dev | ||
| | | | |
hjr265.me
|
|
| | | | | Concurrency is one of the central features of Go. And, to build concurrent programs in Go, you need goroutines. A goroutine is like a thread, but lighter. Much lighter. And, like any other built-in feature of Go, using it is dead simple: 1 2 3 4 5 6 7 package main func main() { go func() { println("Hello World") // Print "Hello World" from a different goroutine. }() } Wait. That didn't print anything. | |
| | | | |
golangbot.com
|
|
| | | | | A Mutex is used to provide a locking mechanism to ensure that only one Goroutine is running the critical section of code at any point in time. Mutexes help avoid race conditions. | |
| | | | |
timilearning.com
|
|
| | | | | This post will contain some examples of good and bad Go code, using them to show common mistakes that can be made when starting to build concurrent programs, and how those can be corrected. It will cover goroutines, mutexes, condition variables, and channels. | |
| | | | |
livesys.se
|
|
| | | |||
