unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Ramin Honary <ramin.honary@gmail.com>
To: guile-devel@gnu.org
Subject: Question: planning support for SRFI-125, SRFI-133?
Date: Mon, 30 Oct 2023 19:24:56 +0900	[thread overview]
Message-ID: <CAFhnQTRRfdsq2Bj00MJ2_1-s9EKiSmsf796Y9XPm_TGq4vcfgw@mail.gmail.com> (raw)

Hello Guile developers:

I have come to realize that there are several finalized SRFIs
published by John Cowan and others, for example, SRFI-133 (vector
library), SRFI-125 (intermediate hash tables), SRFI-126 (R6RS-based
hash tables) that were intended to replace older SRFIs (for example
SRFI-43, and SRFI-69) when R7RS-large is supposed to be ratified.

Looking at the functionality already available in Guile, it seems like
these newer SRFIs could very easily be supported since the
functionality is already fully implemented and could be re-exported as
modules in the (srfi srfi-*) modules. And incidentally, GNU/MIT Scheme
does provide support for SRFI-125 and SRFI-133 already.

So I am wondering why this hasn't been done in Guile yet? Is it a lack
of time and human resources? Or is it somehow against the Guile
philosophy to try to implement these newer SRFIs? Or maybe you want to
wait until R7RS-large is ratified?

If it is a lack of resources, I might like to try implementing these
SRFIs in Guile and submit a patch.

Thanks for your time and hard work implementing Guile!

-- Ramin Honary



             reply	other threads:[~2023-10-30 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 10:24 Ramin Honary [this message]
2023-10-30 17:18 ` Question: planning support for SRFI-125, SRFI-133? Taylan Kammer
2023-10-31 12:48 ` Maxim Cournoyer

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=CAFhnQTRRfdsq2Bj00MJ2_1-s9EKiSmsf796Y9XPm_TGq4vcfgw@mail.gmail.com \
    --to=ramin.honary@gmail.com \
    --cc=guile-devel@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).