Re: [PATCHv3] Extensions for SRFI-171 (Transducers)

[Colin Woodbury <colin@fosskers.ca>]

On 8/18/23 19:03, Ludovic Courtès wrote:
> Apologies for the delays, we’re pioneering “slow dev” I guess.  :-)

Haha no issue at all!

 > Could you take a look?

In that case, please hold on the patch. I am currently "rounding out" 
the "one true Transducer API" in several other Lisps, and am close to 
what I consider a representative set of the desirable primitives a 
developer would want out-of-the-box. One I'm done there, I will return 
to this and a few things that are currently missing.

The other Lisps have also achieved a zip-like pattern (i.e. passing 
multiple collections to `transduce` at the same time, thus allowing 
functions like `map` to operate on multiple inputs).

There is also the issue of SRFI-171's disambiguated `transduce-list`, 
`transduce-vector`, etc., since Scheme has no `defgeneric` by default. 
Guile _does_ however, so we could write a generic `transduce` in Guile's 
own extensions. In general though it would be nice if SRFI-XYZ 
"Transducers Redux" could depend on a standardized generics system, but 
alas.

Anyway, thanks for getting back to me. I'll return to this effort in due 
time.

Cheers,

Colin