---

yaml
---
r: 228998
b: refs/heads/try
c: d8f460c
h: refs/heads/master
v: v3

Author: Gankra

[refs]

@@ -1,7 +1,7 @@
 ---
 refs/heads/master: aca2057ed5fb7af3f8905b2bc01f72fa001c35c8
 refs/heads/snap-stage3: 1af31d4974e33027a68126fa5a5a3c2c6491824f
-refs/heads/try: 2e653f3cce3e5a75861c7c6b9b08729f16b967bf
+refs/heads/try: d8f460c29d6b7e07775562e2090f3f36c6d651e0
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/try/concurrency.md

@@ -10,4 +10,4 @@ them tends to involve trade-offs that we weren't willing to commit to for 1.0.
 However the way Rust models concurrency makes it relatively easy design your own
 concurrency paradigm as a library and have *everyone else's* code Just Work
 with yours. Just require the right lifetimes and Send and Sync where appropriate
-and you're off to the races. Or rather, not having races. Races are bad.
+and you're off to the races. Or rather, off to the... not... having... races.