Go Package sync: Difference between revisions
(→Pool) |
(→Map=) |
||
Line 21: | Line 21: | ||
==<tt>Pool</tt>== | ==<tt>Pool</tt>== | ||
{{Internal|Go Pool|<tt>Pool</tt>}} | {{Internal|Go Pool|<tt>Pool</tt>}} | ||
==<tt>Map</tt> | ==<tt>Map</tt>== | ||
{{External|https://pkg.go.dev/sync#Map}} | {{External|https://pkg.go.dev/sync#Map}} | ||
Revision as of 21:51, 20 January 2024
External
Internal
Overview
The sync
package provides memory access and execution synchronization primitives to use when synchronization between goroutines is necessary. However, other than the Once
and WaitGroup
types, most sync
primitives are intended for use by low-level library routines. Higher level synchronization is better done via channels and communication. Regarding Mutexes, the sync
package implements them, but the language designers expressed their hope that Go programming style will encourage people to try higher-level techniques. In particular, programmers should structure their program so that only one goroutine at a time is ever responsible for a particular piece of data.
Do not communicate by sharing memory. Instead, share memory by communicating.
Also see: