Explore >> Select a destination
|
You are here 
|
mfbmina.dev | ||
| | | | |
hjr265.me
|
|
| | | | | Go provides sync.Mutex as its implementation of a mutual exclusion lock. However, it is not the only synchronization construct that is a part of the standard library. This blog post will look at four synchronization constructs that we can use instead of a sync.Mutex. Counter You may often see code using a sync.Mutex to synchronize access to a counter variable from multiple goroutines. Like this: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 var ( n int m sync. | |
| | | | |
cep.dev
|
|
| | | | | A small post with a bit of Go trivia | |
| | | | |
blog.nuculabs.de
|
|
| | | | | Hi ?? In this article I want to highlight a simple pattern for sorting a slice in Go on multiple keys. Given the following structure, let's say we want to sort it in ascending order after Version, Generation and Time. 1 2 3 4 5 type TheStruct struct { Generation int Time int Version int } The way we sort slices in Go is by using the sort interface or one of the sort.Slice functions. To sort the slice after the above criteria we'll call slice.Sort with the following function. | |
| | | | |
hjr265.me
|
|
| | | In Windows, unlike the Unix-like POSIX-compatible operating systems, there is this notion of an application subsystem: console vs. windows. If you build a Go program for Windows, it will, by default, use the console subsystem. When you start this program from File Explorer (e.g. by double-clicking its icon), Windows will show a console (like the Command Prompt window) and run the program inside the console. When running a console subsystem program that finishes quickly, you may notice the console window appears and disappears quickly. | ||
