This site is a static rendering of the Trac instance that was used by R7RS-WG1 for its work on R7RS-small (PDF), which was ratified in 2013. For more information, see Home.
Source for wiki GeneratorsGauche version 1
author
cowan
comment
ipnr
127.11.51.1
name
GeneratorsGauche
readonly
0
text
{{{
#!html
<h2 class="section">Generators</h2>
<p>A generator is merely a procedure with no arguments and works
as a source of a series of values. Every time it is called,
it yeilds a value. The EOF value indicates the generator is exhausted.
For example, <code>read-char</code> can be seen as a generator that
generates characters from the current input port.
</p>
<p>It is common practice to abstract the source of values in such a way,
so it is useful to define utility procedures that work on the
generators. This module provides them.
</p>
<p>A generator is very lightweight, and handy to implement simple
on-demand calculations. However, keep in mind that it is
side-effecting construct; you can’t safely backtrack, for example..
</p>
<p>You can construct and combine various generators with this module.
Eventually, your code need to consume the generated value.
There are several built-in procedures for that; see
<a href="gauche-refe_58.html#Folding-generated-values">Folding generated values</a>.
</p>
<h3 class="subsection">Generator constructors</h3>
<p>A generator isn’t a special datatype but just an ordinary procedure,
so you can make a generator with lambdas. This module provides
some common generator constructors for the convenience.
</p>
<p>If you want to use your procedure as a generator, note that a
generator can be invoked many times even after it returns EOF once.
You have to code it so that once it returns EOF, it keeps returning
EOF for the subsequent calls.
</p>
<p>The result of generator constructors is merely a procedure,
and printing it doesn’t show much. In the examples in this section
we use <code>generator->list</code> to convert the generator to the list.
See <a href="#Generator-operations">Generator operations</a> for the description of <code>generator->list</code>.
</p>
<dl>
<dt><a name="index-null_002dgenerator"></a><u>Function:</u> <b>null-generator</b></dt>
<dd><p>An empty generator. Returns just an EOF object when called.
</p></dd></dl>
<dl>
<dt><a name="index-circular_002dgenerator"></a><u>Function:</u> <b>circular-generator</b><i> arg …</i></dt>
<dd><p>Returns an infinite generator that repeats the given arguments.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (circular-generator 1 2 3) 10)
⇒ (1 2 3 1 2 3 1 2 3 1)
</pre></td></tr></table>
<p>Note that the above example limits the length of
the converted list by 10; otherwise
<code>generator->list</code> won’t return.
</p></dd></dl>
<dl>
<dt><a name="index-giota"></a><u>Function:</u> <b>giota</b><i> :optional (count +inf.0) (start 0) (step 1)</i></dt>
<dd><p>Like <code>iota</code>, creates a generator
of a series of <var>count</var> numbers, starting from <var>start</var>
and increased by <var>step</var>.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (giota 10 3 2))
⇒ (3 5 7 9 11 13 15 17 19 21)
</pre></td></tr></table>
<p>If both <var>start</var> and <var>step</var> are exact, the generator
yields exact numbers; otherwise it yields inexact numbers.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (giota +inf.0 1/2 1/3) 6)
⇒ (1/2 5/6 7/6 3/2 11/6 13/6)
(generator->list (giota +inf.0 1.0 2.0) 5)
⇒ (1.0 3.0 5.0 7.0 9.0)
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-grange"></a><u>Function:</u> <b>grange</b><i> start :optional (end +inf.0) (step 1)</i></dt>
<dd><p>Similar to <code>giota</code>, creates a generator of a series of
numbers. The series begins with <var>start</var>, increased by <var>step</var>,
and continues while the number is below <var>end</var>.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (grange 3 8))
⇒ (3 4 5 6 7)
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-generate"></a><u>Function:</u> <b>generate</b><i> proc</i></dt>
<dd><p>Creates a generator from coroutine.
</p>
<p>The <var>proc</var> argument is a procedure that takes one argument,
<var>yield</var>. When called, <code>generate</code> immediately returns
a generator <var>G</var>. When <var>G</var> is called, the <var>proc</var> runs
until it calls <var>yield</var>. Calling <var>yield</var> causes to suspend
the execution of <var>proc</var> and <var>G</var> returns the value passed
to <var>yield</var>.
</p>
<p>Once <var>proc</var> returns, it is the end of the series—<var>G</var> returns
eof object from then on. The return value of <var>proc</var> is ignored.
</p>
<p>The following code creates a generator that produces a series
0, 1, and 2 (effectively the same as <code>(giota 3)</code> and binds
it to <code>g</code>.
</p>
<table><tr><td> </td><td><pre class="example">(define g
(generate
(^[yield] (let loop ([i 0])
(when (< i 3) (yield i) (loop (+ i 1)))))))
(generator->list g) ⇒ (0 1 2)
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-list_002d_003egenerator"></a><u>Function:</u> <b>list->generator</b><i> lis :optional start end</i></dt>
<dt><a name="index-vector_002d_003egenerator"></a><u>Function:</u> <b>vector->generator</b><i> vec :optional start end</i></dt>
<dt><a name="index-reverse_002dvector_002d_003egenerator"></a><u>Function:</u> <b>reverse-vector->generator</b><i> vec :optional start end</i></dt>
<dt><a name="index-string_002d_003egenerator"></a><u>Function:</u> <b>string->generator</b><i> str :optioanl start end</i></dt>
<dd><p>Returns a generator that yields each item in the given argument.
A generator returned from <code>reverse-*</code> procedures runs in
reverse order.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (list->generator '(1 2 3 4 5)))
⇒ (1 2 3 4 5)
(generator->list (vector->generator '#(1 2 3 4 5)))
⇒ (1 2 3 4 5)
(generator->list (reverse-vector->generator '#(1 2 3 4 5)))
⇒ (5 4 3 2 1)
(generator->list (string->generator "abcde"))
⇒ (#\a #\b #\c #\d #\e)
</pre></td></tr></table>
<p>By default the generator is exhausted once all items are retrieved;
the optional <var>start</var> and <var>end</var> arguments can limit the range
the generator walks across; <var>start</var> specifies the left bound
and <var>end</var> specifies the right bound.
</p>
<p>For forward generators, the first value the generator yields
is <var>start</var>-th element, and it ends right before <var>end</var>-th element.
For reverse generators, the first value is the item right next
to the <var>end</var>-th element, and the last value is the <var>start</var>-th
element.
at the last element, and reverse generators ends at the first element.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (vector->generator '#(a b c d e) 2))
⇒ (c d e)
(generator->list (vector->generator '#(a b c d e) 2 4))
⇒ (c d)
(generator->list (reverse-vector->generator '#(a b c d e) 2))
⇒ (e d c b)
(generator->list (reverse-vector->generator '#(a b c d e) 2 4))
⇒ (d c)
(generator->list (reverse-vector->generator '#(a b c d e) #f 2))
⇒ (b a)
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-bits_002d_003egenerator"></a><u>Function:</u> <b>bits->generator</b><i> n :optional start end</i></dt>
<dt><a name="index-reverse_002dbits_002d_003egenerator"></a><u>Function:</u> <b>reverse-bits->generator</b><i> n :optional start end</i></dt>
<dd><p>These procedures take an exact integer and treat it as a sequence of
boolean values (0 for false and 1 for true), as <code>integer->list</code> does. <code>Bits->generator</code> takes bits from
LSB, while <code>reverse-bits->generator</code> takes them from MSB.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (bits->generator #b10110))
⇒ (#f #t #t #f #t)
(generator->list (reverse-bits->generator #b10110))
⇒ (#t #f #t #t #f)
</pre></td></tr></table>
<p>The optional <var>start</var> and/or <var>end</var> arguments are used to specify
the range of bitfield, LSB being 0. Unlike <code>list->generator</code> etc,
<var>start</var> specifies the rightmost position (inclusive) and
<var>end</var> specfies the leftmost position (exclusive). It is consistent
with other procedures that accesses bit fields in integers.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (bits->generator #x56 0 4)
⇒ (#f #t #t #f) ; takes bit 0, 1, 2 and 3
(generator->list (bits->generator #x56 4 8)
⇒ (#t #f #t #f) ; takes bit 4, 5, 6 and 7
(generator->list (reverse-bits->generator #x56 4 8)
⇒ (#f #t #f #t) ; takes bit 7, 6, 5 and 4
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-port_002d_003esexp_002dgenerator"></a><u>Function:</u> <b>port->sexp-generator</b><i> input-port</i></dt>
<dt><a name="index-port_002d_003eline_002dgenerator"></a><u>Function:</u> <b>port->line-generator</b><i> input-port</i></dt>
<dt><a name="index-port_002d_003echar_002dgenerator"></a><u>Function:</u> <b>port->char-generator</b><i> input-port</i></dt>
<dt><a name="index-port_002d_003ebyte_002dgenerator"></a><u>Function:</u> <b>port->byte-generator</b><i> input-port</i></dt>
<dd><p>Returns a generator that reads characters or bytes from the given
port, respectively. They’re just
<code>(cut read input-port)</code>,
<code>(cut read-line input-port)</code>,
<code>(cut read-char input-port)</code>
and <code>(cut read-byte input-port)</code>, respectively,
but we provide them for completeness.
</p></dd></dl>
<dl>
<dt><a name="index-x_002d_003egenerator"></a><u>Generic function:</u> <b>x->generator</b><i> obj</i></dt>
<dd><p>A generic version to convert any collection <var>obj</var> to a generator
that walks across the <var>obj</var>. Besides, if <var>obj</var> is an input port,
<code>port->char-generator</code> is called.
</p></dd></dl>
<dl>
<dt><a name="index-file_002d_003egenerator"></a><u>Function:</u> <b>file->generator</b><i> filename reader . open-args</i></dt>
<dd><p>Opens a file <var>filename</var>, and returns a generator
that reads items from the file
by a procedure <var>reader</var>, which takes one argument, an input port.
The arguments <var>open-args</var> are passed to <code>open-input-file</code>
</p>
<p>The file is closed when the generator is exhausted. If a generator
is abandoned before being read to the end, then the file is kept
open until the generator is garbage-collected. If you want to
make sure the file is closed by a certain point of time, you might want
to use a reader procedure as a generator within the dynamic extent
of <code>with-input-from-file</code> etc.
</p></dd></dl>
<dl>
<dt><a name="index-file_002d_003esexp_002dgenerator"></a><u>Function:</u> <b>file->sexp-generator</b><i> filename . open-args</i></dt>
<dt><a name="index-file_002d_003echar_002dgenerator"></a><u>Function:</u> <b>file->char-generator</b><i> filename . open-args</i></dt>
<dt><a name="index-file_002d_003eline_002dgenerator"></a><u>Function:</u> <b>file->line-generator</b><i> filename . open-args</i></dt>
<dt><a name="index-file_002d_003ebyte_002dgenerator"></a><u>Function:</u> <b>file->byte-generator</b><i> filename . open-args</i></dt>
<dd><p>Returns a generator that reads a series
of sexps, characters, lines and bytes from a file <var>filename</var>,
respectively. These are versions
of <code>file->generator</code> specialized by <code>read</code>,
<code>read-char</code>, <code>read-line</code> and <code>read-byte</code> as the
<var>reader</var> argument.
</p>
<p>Like <code>file->generator</code>, <var>open-args</var>
are passed to <code>open-input-file</code>.
The file is closed when the generator is exhausted.
</p></dd></dl>
<dl>
<dt><a name="index-gunfold"></a><u>Function:</u> <b>gunfold</b><i> p f g seed :optional tail-gen</i></dt>
<dd><p>A generator constructor similar to <var>unfold</var>.
</p>
<p><var>P</var> is a predicate that takes a seed value and determines
where to stop. <var>F</var> is a procedure that calculates a value
from a seed value. <var>G</var> is a procedure that calculates the
next seed value from the current seed value. <var>Tail-gen</var>
is a procedure that takes the last seed value and returns a generator
that generates the tail.
</p>
<p>For each call of the resulting generator, <var>p</var> is called with
the current seed value. If it returns a true, then we see we’ve
done, and <code>tail-gen</code> is called (if it is given) to get a
generator for the tail. Otherwise,
we apply <var>f</var> on the current seed value to get the value to
generate, and use <var>g</var> to update the seed value.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (gunfold (^s (> s 5)) (^s (* s 2)) (^s (+ s 1)) 0))
⇒ '(0 2 4 6 8 10)
</pre></td></tr></table>
</dd></dl>
<h3 class="subsection">Generator operations</h3>
<dl>
<dt><a name="index-generator_002d_003elist"></a><u>Function:</u> <b>generator->list</b><i> generator :optional k</i></dt>
<dd><p>Reads items from <var>generator</var> and returns a list of them.
By default, this reads until the generator is exhausted. If
an optional argument <var>k</var> is given, it must be a nonnegative
integer, and the list ends either <var>k</var> items are read,
or the generator is exhausted.
</p>
<p>Be careful not to pass an infinite generator to this without
specifying <var>k</var>—this procedure won’t return but hogs
all the memory before crash.
</p></dd></dl>
<dl>
<dt><a name="index-glet_002a"></a><u>Macro:</u> <b>glet*</b><i> (binding …) body body2 …</i></dt>
<dd><p>This captures a monadic pattern frequently appears in the generator
code. It is in a similar spirit of <code>and-let*</code>, but returns
as soon as the evaluating expression returns EOF, instead of <code>#f</code>
as <code>and-let*</code> does.
</p>
<p>The <var>binding</var> part can be either <code>(var expr)</code> or <code>( expr )</code>.
The actual definition will explain this syntax clearly.
</p>
<table><tr><td> </td><td><pre class="example">(define-syntax glet*
(syntax-rules ()
[(_ () body body2 ...) (begin body body2 ...)]
[(_ ([var gen-expr] more-bindings ...) . body)
(let1 var gen-expr
(if (eof-object? var)
var
(glet* (more-bindings ...) . body)))]
[(_ ([ gen-expr ] more-bindings ...) . body)
(let1 var gen-expr
(if (eof-object? var)
var
(glet* (more-bindings ...) . body)))]))
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-glet1"></a><u>Macro:</u> <b>glet1</b><i> var expr body body2 …</i></dt>
<dd><p>This is to <code>glet*</code> as <code>let1</code> is to <code>let*</code>. In other words,
it is <code>(glet* ([var expr]) body body2 …)</code>.
</p></dd></dl>
<dl>
<dt><a name="index-do_002dgenerator"></a><u>Macro:</u> <b>do-generator</b><i> (var gexpr) body …</i></dt>
<dd><p>This is a generator version of <code>dolist</code> and <code>dotimes</code>.
</p>
<p><var>Gexpr</var> is an expression that yields a generator. It is
evaluated once. The resulting generator is called repeatedly
until it returns EOF. Every time the generator is called,
<var>body</var> … are evaluated in the scope
where <var>var</var> is bound to the value yielded from the generator.
</p>
<p>Like <code>dolist</code> and <code>dotimes</code>, this macro exists for
side-effects. You can write the same thing with <code>for-each</code> families,
but sometimes this macro makes the imperative code more readable:
</p>
<table><tr><td> </td><td><pre class="example">(do-generator [line (file->line-generator "filename")]
;; do some side-effecting stuff with line
)
</pre></td></tr></table>
</dd></dl>
<p>The following procedures take generators (noted as <var>gen</var> and
<var>gen2</var>) and return a generator. For the convenience, they
also accept any collection to <var>gen</var> and <var>gen2</var> parameters;
if a collection is passed where a generator is expected,
it is implicitly coerced into a generator.
</p>
<dl>
<dt><a name="index-gcons_002a"></a><u>Function:</u> <b>gcons*</b><i> item … gen</i></dt>
<dd><p>Returns a generator that adds <var>item</var>s in front of <var>gen</var>.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (gcons* 'a 'b (giota 2)))
⇒ (a b 0 1)
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-gappend"></a><u>Function:</u> <b>gappend</b><i> gen …</i></dt>
<dd><p>Returns a generator that yields the items from the first given
generator, and once it is exhausted, use the second generator, and so on.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (gappend (giota 3) (giota 2)))
⇒ (0 1 2 0 1)
(generator->list (gappend))
⇒ ()
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-gconcatenate"></a><u>Function:</u> <b>gconcatenate</b><i> gen</i></dt>
<dd><p>The <var>gen</var> argument should generate generators and/or sequences.
Returns a generator that yields elements from the first generator/sequence,
then the second one, then the third, etc.
</p>
<p>It is similar to <code>(apply gappend (generator->list gen))</code>, except
that <code>gconcatenate</code> can work even <var>gen</var> generates infinite
number of generators.
</p>
<table><tr><td> </td><td><pre class="example">($ generator->list $ gconcatenate
$ list->generator `(,(giota 3) ,(giota 2)))
⇒ (0 1 2 0 1)
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-gmerge"></a><u>Function:</u> <b>gmerge</b><i> less-than gen gen2 …</i></dt>
<dd><p>Creates a generator that yields elements out of input generators,
with the order determined by a procedure <code>less-than</code>.
The procedure is called as
<code>(less-than a b)</code> and
must return <code>#t</code> iff the element <code>a</code> must precede
the element <code>b</code>.
</p>
<p>Each input generator must yield an ordered elements by itself;
otherwise the result won’t be ordered.
</p>
<p>If only one generator is given, it is just returned (after coercing the
input to a generator). In that case, <code>less-than</code> won’t be called at all.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (gmerge < '(1 3 8) '(5) '(2 4)))
⇒ '(1 2 3 4 5 8)
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-gmap"></a><u>Function:</u> <b>gmap</b><i> proc gen gen2 …</i></dt>
<dd><p>Returns a generator that yields a value returned by <var>proc</var>
applied on the values from given generators. The returned generator
terminates when any of the given generator is exhausted.
</p>
<p>NB: This differs from <code>generator-map</code>,
which consumes all
values at once and returns the results as a list, while <code>gmap</code>
returns a generator immediately without consuming input.
</p></dd></dl>
<dl>
<dt><a name="index-gmap_002daccum"></a><u>Function:</u> <b>gmap-accum</b><i> proc seed gen gen2 …</i></dt>
<dd><p>A generator version of <code>map-accum</code>,
mapping with states.
</p>
<p>The <var>proc</var> argument is a procedure that takes as many arguments
as the input generators plus one. It is called as
<code>(proc v v2 … seed)</code> where <code>v</code>, <code>v2</code>, … are
the values yielded from the input generators, and <var>seed</var> is the
current seed value. It must return two values, the yielding value
and the next seed.
</p></dd></dl>
<dl>
<dt><a name="index-gfilter"></a><u>Function:</u> <b>gfilter</b><i> pred gen</i></dt>
<dd><p>Returns a generator that yield the items from the source generator,
except those who makes <var>pred</var> answers false.
</p></dd></dl>
<dl>
<dt><a name="index-gfilter_002dmap"></a><u>Function:</u> <b>gfilter-map</b><i> proc gen gen2 …</i></dt>
<dd><p>Works the same as <code>(gfilter values (gmap proc gen gen2 …))</code>,
only slightly efficiently.
</p></dd></dl>
<dl>
<dt><a name="index-gstate_002dfilter"></a><u>Function:</u> <b>gstate-filter</b><i> proc seed gen</i></dt>
<dd><p>This allows stateful filtering of a series. The <var>proc</var> argument
must be a procedure that takes a value <var>V</var> from the source generator and
a seed value. It should return two values, a boolean flag and the next
seed value. If it returns true for the boolean flag, the generator
yields <var>V</var>. Otherwise, the generator keeps calling <var>proc</var>,
with updating the seed value, until it sees the true flag value
or the source generator is exhausted.
</p>
<p>The following example takes a generator of oscillating values
and yields only values that are greater than their previous value.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list
(gstate-filter (^[v s] (values (< s v) v)) 0
(list->generator '(1 2 3 2 1 0 1 2 3 2 1 0 1 2 3))))
⇒ (1 2 3 1 2 3 1 2 3)
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-gbuffer_002dfilter"></a><u>Function:</u> <b>gbuffer-filter</b><i> proc seed gen :optional tail-gen</i></dt>
<dd><p>This procedure allows n-to-m mapping between elements in input and output—
that is, you can take a look at serveral input elements to generate
one or more output elements.
</p>
<p>The procedure <var>proc</var> receives the next input element and accumulated
seed value. It returns two values: A list of output values, and the next
seed value. If you need to look at more input to generate
output, you can return an empty list as the first value.
</p>
<p>If the input reaches the end, <var>tail-gen</var> is called with the
current seed value; it should return a list of last output values.
If omitted, the output ends when the output of the last call to <var>proc</var>
is exhausted (the last seed value is discarded).
</p>
<p>Suppose you have a text file. Each line contains a command,
but if the line ends with backslash, next line is treated as a
continuation of the current line. The following code creates
a generator that returns <em>logical</em> lines, that is,
the lines after such line continuations are taken care of.
</p>
<table><tr><td> </td><td><pre class="example">(gbuffer-filter (^[v s]
(if-let1 m (#/\\$/ v)
(values '() (cons (m 'before) s))
(values `(,(string-concatenate-reverse (cons v s))) '())))
'()
(file->line-generator "input-file.txt")
(^[s] `(,(string-concatenate-reverse s))))
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-gtake"></a><u>Function:</u> <b>gtake</b><i> gen k :optional (fill? #f) (padding #f)</i></dt>
<dt><a name="index-gdrop"></a><u>Function:</u> <b>gdrop</b><i> gen k</i></dt>
<dd><p>The generator version of
<code>take*</code> and <code>drop*</code>;
<code>gtake</code> returns a generator that yields (at most) first <var>k</var> items
of the source generator, while <code>gdrop</code> returns a generator
that skips the first <var>k</var> items of the source generator.
</p>
<p>Those won’t complain if the source generator is exhausted before generating
<var>k</var> items. By default, the generator returned by <code>gtake</code>
terminates as the source ends, but if you give a true value to <code>fill?</code>,
then the returned generator does yield <var>k</var> items, using the
<var>padding</var> value to fill the rest.
</p>
<p>Note: If you pass true to <var>fill?</var>, <code>gtake</code> always returns a generator
that generates exactly <var>k</var> elements even the input generator is already
exhausted—there’s no general way to know whether you’ve reached
the end of the input. If you need to take <var>k</var> items repeatedly
from the input generator, you may want to use <code>gslices</code> below.
</p></dd></dl>
<dl>
<dt><a name="index-gtake_002dwhile"></a><u>Function:</u> <b>gtake-while</b><i> pred gen</i></dt>
<dt><a name="index-gdrop_002dwhile"></a><u>Function:</u> <b>gdrop-while</b><i> pred gen</i></dt>
<dd><p>The generator version of <code>take-while</code> and <code>drop-while</code>. The generator returned
from <code>gtake-while</code> yields items from the source generator
as far as <var>pred</var> returns true for each. The generator returned
from <code>gdrop-while</code> first reads items from the source generator
while <var>pred</var> returns true for them, then start yielding items.
</p></dd></dl>
<dl>
<dt><a name="index-gslices"></a><u>Function:</u> <b>gslices</b><i> gen k :optional (fill? #f) (padding #f)</i></dt>
<dd><p>The generator version of <code>slices</code>.
This returns a generator, that yields a list of <var>k</var> items from
the input generator <var>gen</var> at a time.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (gslices (giota 7) 3))
⇒ ((0 1 2) (3 4 5) (6))
</pre></td></tr></table>
<p>The <var>fill?</var> and <var>padding</var> arguments controls how the end
of input is handled, just like <code>gtake</code>. When <var>fill?</var> is
<code>#f</code> (default), the last item from output generator may not
have <var>k</var> items if the input is short to fill them, as shown
in the above example. If <var>fill?</var> is true and the input is
short to complete <var>k</var> items, <var>padding</var> argument is used
to fill the rest.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (gslices (giota 6) 3 #t 'x))
⇒ ((0 1 2) (3 4 5))
(generator->list (gslices (giota 7) 3 #t 'x))
⇒ ((0 1 2) (3 4 5) (6 x x))
</pre></td></tr></table>
</dd></dl>
<h3 class="subsection">Folding generated values</h3>
<p>Generated values needs to be consumed eventually. Here we
provide several procedures to do that. These are useful
when combined with input procedures like <code>read</code>, so we
have them built-in instead of putting them in a separate module.
</p>
<dl>
<dt><a name="index-generator_002dfold"></a><u>Function:</u> <b>generator-fold</b><i> proc seed gen gen2 …</i></dt>
<dd><p>Works like <code>fold</code> on the generated values by generator
procedures <var>gen</var> <var>gen2</var> ….
</p>
<p>When one generator is given, for each value <var>v</var> generated by <var>gen</var>,
<var>proc</var> is called as <code>(<var>proc</var> <var>v</var> <var>r</var>)</code>, where
<var>r</var> is the current accumulated result; the initial value of the
accumulated result is <var>seed</var>,
and the return value from <var>proc</var> becomes the next accumulated result.
When <var>gen</var> returns EOF, the accumulated result at that time is returned
from <code>generator-fold</code>.
</p>
<p>When more than one generator is given, <var>proc</var> is
called as <code>(<var>proc</var> <var>v1</var> <var>v2</var> … <var>r</var>)</code>,
where <var>v1</var>, <var>v2</var> … are the values yielded from
<var>gen</var>, <var>gen2</var>, …, respectively, and <var>r</var> is
the current accumulated result. The iteration terminates when
any one of the generators returns EOF.
</p>
<table><tr><td> </td><td><pre class="example">(with-input-from-string "a b c d e"
(cut generator-fold cons 'z read))
⇒ (e d c b a . z)
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-generator_002dfold_002dright"></a><u>Function:</u> <b>generator-fold-right</b><i> proc seed gen gen2 …</i></dt>
<dd><p>Works like <code>fold-right</code> on the generated values by generator
procedures <var>gen</var> <var>gen2</var> …=.
</p>
<p>This is provided for completeness, but it isn’t a good way to
handle generators; in order to combine values right-associatively,
we should read all the values from the generators (until any one
of the generator returns EOF), then start
calling <var>proc</var> as
</p><table><tr><td> </td><td><pre class="example">(proc v0_0 v1_0 ... (proc v0_1 v1_1 ... (proc v0_n v1_n ... seed) ...))
</pre></td></tr></table>
<p>where <var>vn_m</var> is the <var>m</var>-th value yielded by <var>n</var>-th generator.
</p>
<table><tr><td> </td><td><pre class="example">(with-input-from-string "a b c d e"
(cut generator-fold-right cons 'z read))
⇒ (a b c d e . z)
</pre></td></tr></table>
<p>As you see, keeping all intermediate values kind of defeats the
benefit of generators.
</p></dd></dl>
<dl>
<dt><a name="index-generator_002dfor_002deach"></a><u>Function:</u> <b>generator-for-each</b><i> proc gen gen2 …</i></dt>
<dd><p>A generator version of <code>for-each</code>. Repeatedly applies <var>proc</var> on
the values yielded by <var>gen</var>, <var>gen2</var> … until any one of
the generators yields EOF. The values returned from <var>proc</var> are discarded.
</p>
<p>This is a handy procedure to consume generated values with side effects.
</p></dd></dl>
<dl>
<dt><a name="index-generator_002dmap"></a><u>Function:</u> <b>generator-map</b><i> proc gen gen2 …</i></dt>
<dd><p>A generator version of <code>map</code>. Repeatedly applies <var>proc</var> on
the values yielded by <var>gen</var>, <var>gen2</var> … until any one of
the generators yields EOF. The values returned from <var>proc</var>
are collected into a list and returned.
</p>
<table><tr><td> </td><td><pre class="example">(with-input-from-string "a b c d e"
(cut generator-map symbol->string read))
⇒ ("a" "b" "c" "d" "e")
</pre></td></tr></table>
<p>The same effects can be achieved by combining <code>generator->list</code>
and <code>gmap</code>. This procedure
is provided for the backward compatibility.
</p>
<table><tr><td> </td><td><pre class="example">(generator->list (gmap proc gen gen2 …))
</pre></td></tr></table>
</dd></dl>
<dl>
<dt><a name="index-generator_002dfind"></a><u>Function:</u> <b>generator-find</b><i> pred gen</i></dt>
<dd><p>Returns the first item from the generator <var>gen</var> that satisfies
the predicate <var>pred</var>.
</p>
<p>The following example returns the first line matching the regexp
<code>#/XYZ/</code> from the file ‘<tt>foo.txt</tt>’.
</p>
<table><tr><td> </td><td><pre class="example">(with-input-from-file "foo.txt"
(cut generator-find #/XYZ/ read-line))
</pre></td></tr></table>
}}}
time
2014-09-21 10:59:28
version
1