From 7d256d011e17a3046466cc9e74c1cdc2a9ca6ae0 Mon Sep 17 00:00:00 2001 From: Grzegorz Adam Hankiewicz Date: Tue, 22 Jan 2013 00:29:43 +0100 Subject: [PATCH] Fixes rst format for enumerated list in html output. --- doc/manual.txt | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/doc/manual.txt b/doc/manual.txt index 2a79c0f99f..f4a1b5098f 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