From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Howard <christopher.howard@qlfiles.net>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: SRFIs
Date: Mon, 18 Sep 2017 16:49:23 +0200 [thread overview]
Message-ID: <878thcm58s.fsf@gnu.org> (raw)
In-Reply-To: <1505659744.30946.10.camel@qlfiles.net> (Christopher Howard's message of "Sun, 17 Sep 2017 06:49:04 -0800")
Hello Christopher,
Christopher Howard <christopher.howard@qlfiles.net> skribis:
> Hi, I was just wondering if Guile developers are planning to implement
> all the SRFIs eventually, or if they are just picking and choosing a
> few here and there? Put another way, is it just a matter of someone
> volunteering the time to do each SRFI, or are some not being done on
> purpose?
I can’t think of any SRFI being purposefully ignored, so I think it’s
mostly a matter of someone volunteering to do the work.
Ludo’.
next prev parent reply other threads:[~2017-09-18 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 14:49 SRFIs Christopher Howard
2017-09-17 16:04 ` SRFIs Amirouche Boubekki
2017-09-18 14:49 ` Ludovic Courtès [this message]
2017-09-18 15:10 ` SRFIs Christopher Howard
2017-09-18 19:33 ` SRFIs Arne Babenhauserheide
2017-09-18 20:12 ` SRFIs Ludovic Courtès
2017-09-19 20:50 ` SRFIs Taylan Ulrich Bayırlı/Kammer
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=878thcm58s.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=christopher.howard@qlfiles.net \
--cc=guile-user@gnu.org \
/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).