From: "Ludovic Courtès" <ludo@gnu.org>
To: Tomas Volf <~@wolfsden.cz>
Cc: 74030-done@debbugs.gnu.org
Subject: bug#74030: [PATCH] srfi-64: Accept symbols as test group names.
Date: Sat, 26 Oct 2024 19:20:49 +0200 [thread overview]
Message-ID: <87iktevkzy.fsf@gnu.org> (raw)
In-Reply-To: <20241026160651.20915-1-~@wolfsden.cz> (Tomas Volf's message of "Sat, 26 Oct 2024 18:06:51 +0200")
Tomas Volf <~@wolfsden.cz> skribis:
> The specification mandates a string, but with rationale suggesting symbols
> would be a more natural fit.
>
>> In some ways using symbols would be preferable. However, we want
>> human-readable names, and standard Scheme does not provide a way to include
>> spaces or mixed-case text in literal symbols.
>
> Add support for symbols as implementation extension.
>
> * module/srfi/srfi-64.scm (%cmp-group-name): New procedure.
> (test-end): Use it.
I added “for backwards compatibility with the reference implementation”
and credited Daniel for reporting the issue.
Applied, thanks!
Ludo’.
prev parent reply other threads:[~2024-10-26 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 16:06 bug#74030: [PATCH] srfi-64: Accept symbols as test group names Tomas Volf
2024-10-26 17:20 ` 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=87iktevkzy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=74030-done@debbugs.gnu.org \
--cc=~@wolfsden.cz \
/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).