Explore >> Select a destination
|
You are here 
|
machiel.me | ||
| | | | |
blog.fmpwizard.com
|
|
| | | | | ||
| | | | |
mariocarrion.com
|
|
| | | | | Let's learn about Concurrency Patterns in Go: Background Job | |
| | | | |
konradreiche.com
|
|
| | | | | Starting a goroutine is as easy as adding the go keyword in front of a method, but managing the lifecycle of a goroutine is not. If you only need to start a few goroutines and wait for their completion, you are off the hook thanks to sync.WaitGroup. However, what if a goroutine has to run for a specific duration or repeatatly in a loop until the initiating code terminates? Does it matter? After all, if the main goroutine terminates, any other goroutine will also stop. It does matter, because depending on what the goroutines are doing, it might leave your system in an inconsistent or invalid state. Channels are a commonly used to signal to a goroutine that it can shut down, but I often see the use of a signaling channel, for example chan bool or chan struct{}. | |
| | | | |
serokell.io
|
|
| | | Phoenix is the main web framework in the Elixir ecosystem. Learn how it works and what's special about it. | ||
