Explore >> Select a destination
|
You are here 
|
kokada.dev | ||
| | | | |
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{}... | |
| | | | |
www.cppstories.com
|
|
| | | | | In my last two posts in the C++17 STL series, I covered how to use std::optional. This wrapper type (also called "vocabulary type") is handy when you'd like to express that something is 'nullable' and might be 'empty'. For example, you can return std::nullopt to indicate that the code generated an error... but it this the best choice? | |
| | | | |
lukesingham.com
|
|
| | | | | These are my summary notes of 'A Tour of Go' - which is meant for people who are familiar with programming to have a quick tour | |
| | | | |
feertech.com
|
|
| | | In which we write our first simple machine code | ||
