From: Ricardo Wurmus <rekado@elephly.net>
To: Timothy Sample <samplet@ngyro.com>
Cc: guile-user@gnu.org
Subject: Re: Ideas for making Guile easier to approach
Date: Thu, 10 Feb 2022 11:01:15 +0100 [thread overview]
Message-ID: <87y22jujfp.fsf@elephly.net> (raw)
In-Reply-To: <87leyja69x.fsf@ngyro.com>
Timothy Sample <samplet@ngyro.com> writes:
> I remembered that the R7RS Large process was giving library names to
> SRFIs, but it looks like many of them now have a “library name” field in
> their metadata. For instance, see <https://srfi.schemers.org/srfi-2/>,
> which says “library name: and-let*”. Unfortunately, there are conflicts
> (for example, 43 and 133 are both called “vectors”), so we might not be
> able to take their names whole cloth.
Optionally, the SRFI number could be appended to disambiguate:
vectors:43
vectors:133
As a user I would find this less confusing than the plain numbers.
--
Ricardo
next prev parent reply other threads:[~2022-02-10 10:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 12:19 Newbie thoughts on Guile Hall + Guix Blake Shaw
2022-02-08 19:46 ` Chris Vine
2022-02-09 15:18 ` Ideas for making Guile easier to approach Christine Lemmer-Webber
2022-02-09 20:33 ` Daniel Tornabene
2022-02-09 21:05 ` Maxime Devos
2022-02-09 23:06 ` Keith Wright
2022-02-09 21:05 ` Olivier Dion via General Guile related discussions
2022-02-09 21:07 ` Maxime Devos
2023-10-05 14:15 ` Dr. Arne Babenhauserheide
2022-02-09 23:01 ` Chris Vine
2022-02-10 0:56 ` Timothy Sample
2022-02-10 10:01 ` Ricardo Wurmus [this message]
2022-02-10 1:32 ` Blake Shaw
2022-02-10 2:02 ` paul
2022-02-10 11:27 ` Mikael Djurfeldt
2022-02-10 14:34 ` Leo Butler
2022-02-10 15:58 ` Mikael Djurfeldt
2022-02-10 18:25 ` Olivier Dion via General Guile related discussions
2023-09-27 19:29 ` Christine Lemmer-Webber
2023-09-28 12:30 ` Maxime Devos
2022-02-09 6:28 ` Newbie thoughts on Guile Hall + Guix Catonano
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=87y22jujfp.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guile-user@gnu.org \
--cc=samplet@ngyro.com \
/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).