What is the best way to avoid race conditions in struct methods in Go? Are there any practices?

Question

go

I wrote this code. Certainly not thread-safe.

...
func (s *Scanner) incrExtCount(ext string) {
  _, found := s.stats.extFreq[ext]
  if found {
    s.stats.extFreq[ext]++
  } else {
    s.stats.extFreq[ext] = 1
  }
}

func (s *Scanner) addPath(path string) {
  s.stats.recentPaths.PushFront(path)
  s.stats.pathsNum++
  if s.stats.pathsNum > MaxPaths {
    s.stats.recentPaths.Remove(s.stats.recentPaths.Back())
  }
}
...

I can wrap every data read and write operation (line of code) in a mutex lock/unlock, but is that correct?
What type of mutex should be used in this case?

Answer 1

type GuardedScanner struct{
    s *Scanner
    *sync.Mutex //Поскольку метод всегда пишет заморачиваться с RWMutex смысла не вижу
}
func (gs *GuardedScanner) addPath(path string) {
    gs.Lock()
    gs.s.addPath(path)
    gs.Unlock()
}
//В первом методе можно обойтись sync/atomic
...
type stats struct{
...
    extFreq map[string]*uint64
...
}
func (gs *GuardedScanner) incrExtCount(ext string) {
  _, found := s.stats.extFreq[ext]
  if found {
    atomic.AddUint64(gs.stats.extFreq[ext], 1)
  } else {
    atomic.StoreUint64(gs.stats.extFreq[ext], 1)
  }
}