From: "Ludovic Courtès" <ludo@gnu.org>
To: "Linus Björnstam" <linus.bjornstam@veryfast.biz>
Cc: Guile Devel <guile-devel@gnu.org>
Subject: Re: [PATCH] Add srfi-171 to guile
Date: Wed, 25 Mar 2020 22:48:14 +0100 [thread overview]
Message-ID: <877dz8gl7l.fsf@gnu.org> (raw)
In-Reply-To: <1b731380-52d0-43ff-b278-95461205161c@www.fastmail.com> ("Linus \=\?utf-8\?Q\?Bj\=C3\=B6rnstam\=22's\?\= message of "Mon, 23 Mar 2020 18:17:16 +0100")
Hi Linus,
Linus Björnstam <linus.bjornstam@veryfast.biz> skribis:
> From 1450661c2432522ee41b43dffd05e46384a3ff1b Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Linus=20Bj=C3=B6rnstam?= <linus.bjornstam@fastmail.se>
> Date: Mon, 23 Mar 2020 14:59:39 +0100
> Subject: [PATCH] Add SRFI-171 to guile
>
> This adds SRFI-171 (transducers) to guile.
>
> The two guile-specific additions are powerful transducers which can be
> used to generalize transducers like tsegment. They are hard to get
> right, but powerful and useful enough to warrant inclusion.
>
> * doc/ref/srfi-modules.texi: added srfi-171 section
> * module/Makefile.am (SOURCES):
> * module/srfi/srfi-171.scm:
> * module/srfi/srfi-171/meta.scm: Add SRFI-171
> * module/srfi/srfi-171/gnu.scm: Add 2 guile-specific extensions.
> * test-suite/Makefile.am (SCM_TESTS):
> * test-suite/tests/srfi-171.test: Add tests.
Perfect, applied! It’s great to have this part of Guile proper.
Thank you!
Ludo’.
prev parent reply other threads:[~2020-03-25 21:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-22 14:55 [PATCH] Add srfi-171 to guile Linus Björnstam
2019-12-22 20:45 ` Linus Björnstam
2020-01-05 11:30 ` Andy Wingo
2020-01-05 13:34 ` Linus Björnstam
2020-01-16 19:52 ` Linus Björnstam
2020-03-08 14:40 ` Ludovic Courtès
2020-03-08 17:11 ` Linus Björnstam
2020-03-23 17:17 ` Linus Björnstam
2020-03-25 21:48 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dz8gl7l.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=linus.bjornstam@veryfast.biz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).