Coroutine

gto76 · gto76 · commit 6f5789c8068c · 2019-07-29T04:19:01.000+02:00
diff --git a/README.md b/README.md
@@ -2145,14 +2145,14 @@ ValueError: malformed node or string
 
 Coroutine
 ---------
-* **Similar to generator, but generator pulls data through the pipe with iteration, while coroutine pushes data into the pipeline with send().**
+* **Any function that contains a `'(yield)'` expression returns a coroutine.**
+* **Coroutines are similar to iterators, but data needs to be pulled out of an iterator by calling `'next(<iter>)'`, while we push data into the coroutine by calling `'<coroutine>.send(<el>)'`.**
 * **Coroutines provide more powerful data routing possibilities than iterators.**
-* **If you build a collection of simple data processing components, you can glue them together into complex arrangements of pipes, branches, merging, etc.**
 
 ### Helper Decorator
-* **All coroutines must be "primed" by first calling next().**
+* **All coroutines must first be "primed" by calling `'next(<coroutine>)'`.**
 * **Remembering to call next() is easy to forget.**
-* **Solved by wrapping coroutines with a decorator:**
+* **Solved by wrapping functions that return a coroutine with a decorator:**
 
 ```python
 def coroutine(func):
diff --git a/index.html b/index.html
@@ -1858,13 +1858,13 @@
 </code></pre></div>
 
 <div><h2 id="coroutine"><a href="#coroutine" name="coroutine">#</a>Coroutine</h2><ul>
-<li><strong>Similar to generator, but generator pulls data through the pipe with iteration, while coroutine pushes data into the pipeline with send().</strong></li>
+<li><strong>Any function that contains a <code class="python hljs"><span class="hljs-string">'(yield)'</span></code> expression returns a coroutine.</strong></li>
+<li><strong>Coroutines are similar to iterators, but data needs to be pulled out of an iterator by calling <code class="python hljs"><span class="hljs-string">'next(&lt;iter&gt;)'</span></code>, while we push data into the coroutine by calling <code class="python hljs"><span class="hljs-string">'&lt;coroutine&gt;.send(&lt;el&gt;)'</span></code>.</strong></li>
 <li><strong>Coroutines provide more powerful data routing possibilities than iterators.</strong></li>
-<li><strong>If you build a collection of simple data processing components, you can glue them together into complex arrangements of pipes, branches, merging, etc.</strong></li>
 </ul><div><h3 id="helperdecorator">Helper Decorator</h3><ul>
-<li><strong>All coroutines must be "primed" by first calling next().</strong></li>
+<li><strong>All coroutines must first be "primed" by calling <code class="python hljs"><span class="hljs-string">'next(&lt;coroutine&gt;)'</span></code>.</strong></li>
 <li><strong>Remembering to call next() is easy to forget.</strong></li>
-<li><strong>Solved by wrapping coroutines with a decorator:</strong></li>
+<li><strong>Solved by wrapping functions that return a coroutine with a decorator:</strong></li>
 </ul><pre><code class="python language-python hljs"><span class="hljs-function"><span class="hljs-keyword">def</span> <span class="hljs-title">coroutine</span><span class="hljs-params">(func)</span>:</span>
     <span class="hljs-function"><span class="hljs-keyword">def</span> <span class="hljs-title">out</span><span class="hljs-params">(*args, **kwargs)</span>:</span>
         cr = func(*args, **kwargs)
