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

2023-08-18 Thread Ludovic Courtès
Hello, Colin Woodbury skribis: > 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

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

2023-08-18 Thread Colin Woodbury
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

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

2023-08-18 Thread Ludovic Courtès
Hi Colin, Colin Woodbury skribis: > Hi again, any thoughts on these SRFI-171 extensions? Looong ago, before we waited for copyright assignment to be on file, I made minor suggestions on the patch, which I think you haven’t responded to: https://lists.gnu.org/archive/html/guile-devel/2023-01/

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

2023-08-12 Thread Colin Woodbury
On 8/13/23 04:37, Linus Björnstam wrote: Hi! I have finally started getting some computer time again, and I will make sure to get this into some kind of extra library in the official SRFI repo. It will not be official, but maybe for a future SRFI based on SRFI 171. Hi Linus, good to hear

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

2023-08-12 Thread Linus Björnstam
Hi! I have finally started getting some computer time again, and I will make sure to get this into some kind of extra library in the official SRFI repo. It will not be official, but maybe for a future SRFI based on SRFI 171. -- Linus Björnstam On Wed, 28 Jun 2023, at 14:27, Colin Woodbur

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

2023-06-28 Thread Colin Woodbury
Hi again, any thoughts on these SRFI-171 extensions? On 5/18/23 09:36, Colin Woodbury wrote: Hi! Forgive the delay; my copyright assignment for Guile has finally gone through. Please let me know if the patches are still good! Colin On 1/24/23 18:07, Ludovic Courtès wrote: Hi Colin, Colin Wo

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

2023-05-17 Thread Colin Woodbury
Hi! Forgive the delay; my copyright assignment for Guile has finally gone through. Please let me know if the patches are still good! Colin On 1/24/23 18:07, Ludovic Courtès wrote: Hi Colin, Colin Woodbury skribis: Sorry if I wasn't clear - I have alright assigned copyright to the FSF (abou

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

2023-01-24 Thread Ludovic Courtès
Hi Colin, Colin Woodbury skribis: > Sorry if I wasn't clear - I have alright assigned copyright to the FSF > (about 1.5 years ago). Things should be good to go, unless I've > misunderstood. I checked the records on fencepost.gnu.org and AFAICS, you assigned copyright for Emacs only (copyright a

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

2023-01-23 Thread Colin Woodbury
Hi Ludovic, Sorry if I wasn't clear - I have alright assigned copyright to the FSF (about 1.5 years ago). Things should be good to go, unless I've misunderstood. Cheers, Colin On 1/24/23 07:17, Ludovic Courtès wrote: Hi Colin, Colin Woodbury skribis: Hi Ludovic, thanks for getting back

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

2023-01-23 Thread Ludovic Courtès
Hi Colin, Colin Woodbury skribis: > Hi Ludovic, thanks for getting back to me! I've updated the patches as > you've suggested. I think I've gotten the commit format correct this > time. Yup, it’s looks perfect! > Also, I'll opt to assign copyright to the FSF, as I've already done so > for Emac

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

2023-01-20 Thread Colin Woodbury
Hi Ludovic, thanks for getting back to me! I've updated the patches as you've suggested. I think I've gotten the commit format correct this time. Also, I'll opt to assign copyright to the FSF, as I've already done so for Emacs (and signed the papers, etc.). Let there be transduction! Cheers,