From eefab15c724310192e5dcf392ae446d4ed090613 Mon Sep 17 00:00:00 2001 From: Mark McGranaghan Date: Mon, 7 Oct 2013 06:02:02 -0700 Subject: [PATCH] rebuild --- examples/atomic-counters/atomic-counters.hash | 4 ++-- public/atomic-counters | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/examples/atomic-counters/atomic-counters.hash b/examples/atomic-counters/atomic-counters.hash index c62b86e..e1cec67 100644 --- a/examples/atomic-counters/atomic-counters.hash +++ b/examples/atomic-counters/atomic-counters.hash @@ -1,2 +1,2 @@ -97f1f28e352163cb841fb26dc05dced9fa8efde5 -sKIaNsJquU +ddfef8425eef64cfcb82799c9bddca4bfa9bbd29 +2h8nvrnaHP diff --git a/public/atomic-counters b/public/atomic-counters index 174cc61..c61be6b 100644 --- a/public/atomic-counters +++ b/public/atomic-counters @@ -27,7 +27,7 @@

The primary mechanism for managing state in Go is communication over channels. We saw this for example -with worker pools. There are a few other +with worker pools. There are a few other options for managing state though. Here we’ll look at using the sync/atomic package for atomic counters accessed by multiple goroutines.

@@ -44,7 +44,7 @@ counters accessed by multiple goroutines.

- + 
package main