A data race yana faruwa lokacin da goroutines biyu ko fiye suke shiga alawar gayya mai kama a jiya-jiya, akalla ɗaya daga shigigai shine rubuta, kuma babu haɗin gida tsakaninsu. Sakamakon haka shi ne jigon halin da bai bayyana ba — lalacewar bayani, fashe-fashe, ko sakamakon da bai dace ba da ake kira a waje-waje. Go tana ba da race detector ta gida don nemo su.
// ❌ DATA RACE — multiple goroutines write the same variable without synchronization
func main() {
counter := 0
var wg sync.WaitGroup
for i := 0; i < 1000; i++ {
wg.Add(1)
go func() {
defer wg.Done()
counter++ // RACE: read-modify-write, multiple goroutines at once
}()
}
wg.Wait()
fmt.Println(counter) // often NOT 1000 — updates are lost due to the race
}
counter++ shi ne karanta-canja-rubuta (mataki uku). Lokacin da goroutines suke tarawa, sauyi suna bugi juna, don haka lissafin azali ba sa sani. Sakamakon haka yana banbanta tsakanin gudu — halaye mara kyau na races.
go run -race main.go # run with race detection enabled
go test -race ./... # run tests with the race detector (best practice in CI)
go build -race # build a race-detecting binary
The race detector reports each race it observes:
==================
WARNING: DATA RACE
Write at 0x... by goroutine 7: main.main.func1() main.go:12
Previous read at 0x... by goroutine 6: ...
==================
Race detector yana bugi ajiyar alawar a lokacin gudu kuma yana ba da rahoton ga yadda race ke faruwa (shigigai da ke gida kuma su goroutines/layi). Shi shi ne daya daga cikin kayan aiki masu mahimmanci na Go — gudde jare-jareki tare da -race (musamman a CI) don kamata races kafin saida.
// Fix 1: protect with a mutex
var mu sync.Mutex
mu.Lock(); counter++; mu.Unlock()
// Fix 2: use atomic operations (lock-free, for simple values)
import "sync/atomic"
var counter int64
atomic.AddInt64(&counter, 1) // atomic — no race
// Fix 3: don't share — use channels to pass ownership
results := make(chan int)
// each goroutine sends its result; one goroutine aggregates
Gyarawa su ne kayan haɗi: mutex don tsara shigarwa, atomic aiki ga iyawa masu sauƙi, ko channels don guje wajen adadi.
✗ NON-DETERMINISTIC — may work in testing, fail in production (timing-dependent)
✗ Hard to reproduce — depends on goroutine scheduling, load, hardware
✗ UNDEFINED behavior — not just wrong values; can corrupt data or crash
✗ Often invisible without the race detector — no error, just subtly wrong results
Data races su ne daga cikin mafi haɗari da mafi wahalar debugging bugs a cikin concurrent Go — kuma nuni ta Go mai haɗari yana sa su kashe gaske.
Su suna kasuwa ne domin su ba mara kyau: lambar da ta kashe ayai zai iya rira duka jare-jareki kuma aiki daidai a ƙarƙar nauyi, sa'an nan ya kashe a lokaci-lokaci a saida a ƙarƙar nauyi, inda ta haɓaka bayani, sakamakon da bai dace ba, ko fashe-fashe da aka ƙarasa da ba ya izin.
\nHankalin ainiyin ma'ana (shigawar taya-taya ga adadin da ke adadi tare da akalla ɗaya da rubuta kuma babu haɗi), ganin cewa har lambar sauƙi kamar counter++ kashe, kuma sanin gyarawa (mutex, atomic, channels) shine dole don rubuta concurrent Go mai daidai.
Ma'ana mahimmanci, race detector na Go (-race) shine kayan aiki da ba za a iya gaje shi ba — gudde jare-jareki tare da shi (ma'ana a CI) kan samu races da baki baki ne.
Rangwamen gano races kuma hana su shine mahimmancin sararin aiki na Go na jiya-jiya kuma daya daga cikin mahimman jihadun na gida, tun da daidaita concurrent ita ce waje da Go lambobi most often ku bugi.