Home > Backend Development > Golang > Why is `append` function not thread-safe for concurrent access in Go?

Why is `append` function not thread-safe for concurrent access in Go?

Patricia Arquette
Release: 2024-11-10 03:50:02
Original
409 people have browsed it

Why is `append` function not thread-safe for concurrent access in Go?

Append Function: Not Thread-Safe for Concurrent Access

When utilizing goroutines concurrently to append elements to a slice within a for loop, anomalies in data can arise. Missing or blank data may appear in the resultant slice, indicating potential data races.

This occurs because in Go, no value is innately safe for simultaneous read and write. Slices, which are represented by slice headers, are no exception. The code provided exhibits data races due to concurrent access:

destSlice := make([]myClass, 0)

var wg sync.WaitGroup
for _, myObject := range sourceSlice {
    wg.Add(1)
    go func(closureMyObject myClass) {
        defer wg.Done()
        var tmpObj myClass
        tmpObj.AttributeName = closureMyObject.AttributeName
        destSlice = append(destSlice, tmpObj)
    }(myObject)
}
wg.Wait()
Copy after login

To verify the presence of data races, execute the following command:

go run -race play.go
Copy after login

The output will alert you to data races:

WARNING: DATA RACE
...
Copy after login

Resolving Concurrency Issues

To resolve this issue, protect the write access to the destSlice by employing a sync.Mutex:

var (
    mu        = &sync.Mutex{}
    destSlice = make([]myClass, 0)
)

var wg sync.WaitGroup
for _, myObject := range sourceSlice {
    wg.Add(1)
    go func(closureMyObject myClass) {
        defer wg.Done()
        var tmpObj myClass
        tmpObj.AttributeName = closureMyObject.AttributeName
        mu.Lock()
        destSlice = append(destSlice, tmpObj)
        mu.Unlock()
    }(myObject)
}
wg.Wait()
Copy after login

Alternatively, consider using a channel to asynchronously handle the appends:

var (
    appendChan = make(chan myClass)
    destSlice  = make([]myClass, 0)
)

var wg sync.WaitGroup
for _, myObject := range sourceSlice {
    wg.Add(1)
    go func(closureMyObject myClass) {
        defer wg.Done()
        var tmpObj myClass
        tmpObj.AttributeName = closureMyObject.AttributeName
        appendChan <- tmpObj
    }(myObject)
}
go func() {
    for {
        tmpObj := <-appendChan
        destSlice = append(destSlice, tmpObj)
    }
}()
wg.Wait()
Copy after login

The above is the detailed content of Why is `append` function not thread-safe for concurrent access in Go?. For more information, please follow other related articles on the PHP Chinese website!

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Latest Articles by Author
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template