[ThatGeoGuy]

An alternative, R7RS implementation that I also maintain for (CHICKEN) Scheme: <https://wiki.call-cc.org/eggref/5/transducers>

I believe I've submitted my own blog post on transducers in the past. See <https://www.thatgeoguy.ca/blog/2023/01/04/reflections-on-tra...>

To bjoli: Have you seen my library? Any intentions to update the SRFI and incorporate more types?

[bjoli]

I have had some plans on updating the SRFI to add some reducers I did not include because I never actually used transducers before writing the initial implementation.

I don't really understand what you mean by types (my implementation stays monomorphic so new types are easily introduced by TYPE-transduce) , but I have thought about generalising things like numerical ranges by having something like unfold-transduce.

[ThatGeoGuy]

> but I have thought about generalising things like numerical ranges by having something like unfold-transduce.

This is more or less what I was wondering about. Numerics, ports, SRFI-41 streams, etc. There's a lot of stuff that isn't in e.g. r7rs-small but is more or less expected in most Scheme implementations.

[bjoli]

Well. Without generic functions it is impossible to specify a "complete" API. I mention it in "Scope considerations" in the srfi document