Changes for version v0.3.3 - 2026-11-16

  • A run costs about half what it did to start and end, so a short run, such as an iterator reading one row, costs 7 to 8 µs less.
  • It ships change record 2026-0040, a task from DBIx-Squirrel, which profiled its handles. Nothing changes but speed: the values, the messages, the order things run in, and what each part is told are as they were.
  • An iterator whose run has no flush, no stage's end and no sink, as most have, takes a shorter way, with none of their bookkeeping: with no stages, $p->iterator($code) let go costs about 8 µs, not 15, and $p->iterator(source {...})->all about 12 µs, not 20, on Perl 5.36 and 5.44 alike. Every run is a little cheaper to set up, and a plain run pulling many values is 3 to 6% faster a value. (change record 2026-0040)

Documentation

Ekorn::Pipeline user guide
Ekorn::Pipeline reference

Modules

run values through a list of stages
what Ekorn's types are made from
report Ekorn::Pipeline's errors at the caller's line
words that make Ekorn's types
a stage made afresh for each run, told when its values run out
one run, handing out its values as they're pulled
read and write JSON and JSON Lines, as sources, stages or sinks
|, |= and @{} for Ekorn's types
pipe and tap methods, running an object through stages
a sink made afresh for each run
ready-made sinks, needing only Perl
a source made afresh for each run
ready-made sources, needing only Perl
a stage, as an object
stages gathering values: batch and collect
stages taking or dropping values: take, drop, take_if, drop_if, take_while and drop_while
stages run for their side effects: peek, count_into and dump_to
end a pipeline early
name pipelines as the program compiles, each with a function
Ekorn's stages, sources, sinks and words, from one module

Provides

in lib/Ekorn/Pipeline/Operators.pm
in lib/Ekorn/Pipeline/Operators.pm
in lib/Ekorn/Pipeline/Sink.pm
in lib/Ekorn/Pipeline/Sink.pm