jyapayne/nim-by-example
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix bug and explain closure iterators better

Browse source
This commit is contained in:
flaviut 2014-07-18 18:53:03 -04:00
commit a868603482
1 changed files with 11 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

14
content/for_iterators.md
View file

@ -84,7 +84,7 @@ $ nimrod c -r ./inline_iter.nim
## Closure Iterators
Closure iterators hold on to their state and can be resumed at any time. The `finished()` function can be used to check if there are any more elements available in the iterator.
Closure iterators hold on to their state and can be resumed at any time. The `finished()` function can be used to check if there are any more elements available in the iterator, however raw iterator usage is unintuitive and difficult to get right.
``` nimrod
proc countTo(n: int): iterator(): int =
@ -99,8 +99,16 @@ let countTo20 = countTo(20)
echo countTo20()
var output = ""
while not finished(countTo20):
output.add($countTo20() & " ")
# Raw iterator usage:
while true:
# 1. grab an element
let next = countTo20()
# 2. Is the element bogus? Its the end of the loop, discard it
if finished(countTo20):
break
# 3. Loop body goes here:
output.add($next & " ")
echo output
output = ""