Clojure should make representing iterated api calls easier


Many apis (elasticsearch, github, s3, etc) have parts of the api
which, in usage, end up being used in an interative way. You make an
api call, and you use the result to make another api call, and so
on. This most often shows up in apis have some concept of pages of
results that you page through, and is very prevalent in http apis.

This appears to be such a common pattern that it would be great if
Clojure had in built support for it.

You may think Clojure already does have support for it, after all,
Clojure has `iterate`. In fact the docstring for `iterate`
specifically says the function you give it must be free of side

I propose adding a function `unfold` to clojure.core to support this
use case. `unfold` would return an implementation of ReduceInit. The
name `unfold` matches what would be a similar Haskell function
and also matches the name for a similar function used in some existing
Clojure libraries

`unfold` in some ways looks like a combination of `take-while` and
`iterate`, except for the fact that `iterate` requires a pure
function. Another possible solution would be a version of `iterate`
that doesn't require a pure function.

It seems like given the use case I envision for `unfold`, a
non-caching reducible would be perfect. But that would leave those
that prefer seqs high and dry, so maybe at least some consideration
should be given to seqs.

Mailing list discussion is here

A sort of dummy api you might want to interact with would look something like

given the above api, if you had an implementation of `unfold` that took a predicate that decided when to continue unfolding, a producer which given a value in a sequence produced the next value, and an initial value, you could do something like this:

and the result would be true.

The equivilant take-while + iterate would be something like:




Ghadi Shayban
June 6, 2016, 2:40 PM

updated patch to apply cleanly to core

Ghadi Shayban
September 19, 2016, 5:40 AM

I'm not sure I'm sold on this anymore, and have suggested a different approach on the mailing list

Ghadi Shayban
April 17, 2017, 7:40 PM

I have been marinating upon two generator functions that cover use-cases including the one listed above.

One of them is similar to Scheme's unfold but with some deviations more appropriate to Clojure. The other function takes a side-effecting producer and a sentinel value.

Ignore the naming and examine the semantics.

Alex Miller
March 31, 2020, 1:04 AM

This ticket is being replaced by the work in

Erik Assum
August 12, 2020, 2:58 PM




Kevin Downey