I see. My experience with detecting and fixing races using that tool, evidently applied to much simpler code, was basically getting notified that some variable

I see. My experience with detecting and fixing races using that tool, evidently applied to much simpler code, was basically getting notified that some variable was being written without synchronization by multiple goroutines, protecting it with a mutex, and being good to go. That's why I assumed linearity between running it and coming to a solution.