diff options
author | Grzegorz Adam Hankiewicz <gradha@imap.cc> | 2013-01-22 00:29:43 +0100 |
---|---|---|
committer | Grzegorz Adam Hankiewicz <gradha@imap.cc> | 2013-01-22 00:31:31 +0100 |
commit | 7d256d011e17a3046466cc9e74c1cdc2a9ca6ae0 (patch) | |
tree | 4efd54479a70896b68218472cb58ac3d3d079ef9 /doc | |
parent | d0bd5d5cc3407e14ff37590077ec40441be26c84 (diff) | |
download | Nim-7d256d011e17a3046466cc9e74c1cdc2a9ca6ae0.tar.gz |
Fixes rst format for enumerated list in html output.
Diffstat (limited to 'doc')
-rwxr-xr-x | doc/manual.txt | 14 |
1 files changed, 6 insertions, 8 deletions
diff --git a/doc/manual.txt b/doc/manual.txt index 2a79c0f99..f4a1b5098 100755 --- a/doc/manual.txt +++ b/doc/manual.txt @@ -2682,16 +2682,14 @@ In contrast to that, a `closure iterator`:idx: can be passed around: invoke(count0) invoke(count2) - Closure iterators have other restrictions than inline iterators: -1.) ``yield`` in a closure iterator can not occur in a ``try`` statement. -2.) For now, a closure iterator cannot be evaluated at compile time. -3.) ``return`` is allowed in a closure iterator (but rarely useful). -4.) Since closure iterators can be used as a collaborative tasking - system, ``void`` is a valid return type for them. -5.) Both inline and closure iterators cannot be recursive. - +1. ``yield`` in a closure iterator can not occur in a ``try`` statement. +2. For now, a closure iterator cannot be evaluated at compile time. +3. ``return`` is allowed in a closure iterator (but rarely useful). +4. Since closure iterators can be used as a collaborative tasking + system, ``void`` is a valid return type for them. +5. Both inline and closure iterators cannot be recursive. Iterators that are neither marked ``{.closure.}`` nor ``{.inline.}`` explicitly default to being inline, but that this may change in future versions of the |