Re: New egg: CHICKEN Transducers

Jeremy Steward writes: > 2. Macro-based: This makes it pretty difficult to extend, especially > if you don't have a clear "standard" or "winning" data structure that > the community can rely on. Not that it's impossible, but I'd have an > easier time as a user writing a custom fold procedure (and

Re: New egg: CHICKEN Transducers

On 1/5/23 09:45, Walter Lewis wrote: On 1/4/23 8:48 PM, Jeremy Steward wrote: And I've written a short blog post outlining some of my frustrations that led me to writing this egg: Happy to engage with the rest of the commu

Re: New egg: CHICKEN Transducers

On 1/5/23 05:49, siiky wrote: Awesomesauce, thanks for the egg and the post! This is a smnall-ish pain point of mine too. I'm still processing the post as well, but I can tell I'll start using this frequently! That's great to hear. I appreciate that you enjoyed the post and will start using tr

Re: New egg: CHICKEN Transducers

On 1/5/23 06:11, siiky wrote: There are some things I would still use SRFI 42 for, at least for now that I'm new to transducers. For example: (list-ec (:list x lst1) (:list y lst2) (if (even? (* x y))) (cons x y)) Which is similar to (filter even (map * lst1 ls

Re: New egg: CHICKEN Transducers

On 1/5/23 04:22, Chris Brannon wrote: Jeremy Steward writes: And I've written a short blog post outlining some of my frustrations that led me to writing this egg: That was a fantastic post. I'm still digesting it. How

Re: New egg: CHICKEN Transducers

On 1/5/23 00:44, Peter Bex wrote: And I've written a short blog post outlining some of my frustrations that led me to writing this egg: Excellent observations, especially regarding the fold argument inconsistency, that's s

Re: New egg: CHICKEN Transducers

On 1/4/23 8:48 PM, Jeremy Steward wrote: And I've written a short blog post outlining some of my frustrations that led me to writing this egg: Happy to engage with the rest of the community on what the next priority for s

Re: New egg: CHICKEN Transducers

How about SRFI 42? I wrote a little bit in #chicken but think it should be added here as well. Pros of SRFI 42: + It's short and clear. It feels very natural to me. Maybe just because I've used it for some time while I've just been introduced to transducers now, but I have the impression th

Re: New egg: CHICKEN Transducers

Awesomesauce, thanks for the egg and the post! This is a smnall-ish pain point of mine too. I'm still processing the post as well, but I can tell I'll start using this frequently! First a couple of typos: In footnote 4 it should be `call/cc` and not `call-cc`? And "its not the Scheme I reach f

Re: New egg: CHICKEN Transducers

Jeremy Steward writes: > And I've written a short blog post outlining some of my frustrations > that led me to writing this egg: > > That was a fantastic post. I'm still digesting it. How about SRFI 42? Here's your example

General comments

Arguably that's a feature - in Scheme you'll always be sure of the performance characteristics of the type you're working with, and you'll always know what type you're working with. Also, by not having generics for collection types you avoid quite a performance overhead related to dispatch. But I