yeray/gobyexample
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

rebuild

Browse Source
This commit is contained in:
Mark McGranaghan 2013-10-07 06:02:02 -07:00
parent 46fbbfda0f
commit eefab15c72
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
examples/atomic-counters/atomic-counters.hash
View File

@ -1,2 +1,2 @@
97f1f28e352163cb841fb26dc05dced9fa8efde5 ddfef8425eef64cfcb82799c9bddca4bfa9bbd29
sKIaNsJquU 2h8nvrnaHP

4
public/atomic-counters
View File

@ -27,7 +27,7 @@
<td class="docs"> <td class="docs">
<p>The primary mechanism for managing state in Go is <p>The primary mechanism for managing state in Go is
communication over channels. We saw this for example communication over channels. We saw this for example
with <a href="worker-pool">worker pools</a>. There are a few other with <a href="worker-pools">worker pools</a>. There are a few other
options for managing state though. Here we&rsquo;ll options for managing state though. Here we&rsquo;ll
look at using the <code>sync/atomic</code> package for <em>atomic look at using the <code>sync/atomic</code> package for <em>atomic
counters</em> accessed by multiple goroutines.</p> counters</em> accessed by multiple goroutines.</p>
@ -44,7 +44,7 @@ counters</em> accessed by multiple goroutines.</p>
</td> </td>
<td class="code leading"> <td class="code leading">
<a href="http://play.golang.org/p/sKIaNsJquU"><img title="Run code" src="play.png" class="run" /></a> <a href="http://play.golang.org/p/2h8nvrnaHP"><img title="Run code" src="play.png" class="run" /></a>
<div class="highlight"><pre><span class="kn">package</span> <span class="nx">main</span> <div class="highlight"><pre><span class="kn">package</span> <span class="nx">main</span>
</pre></div> </pre></div>