unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: lloda <lloda@sarc.name>
To: 73605@debbugs.gnu.org
Cc: "Tomas Volf" <~@wolfsden.cz>, "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#73605: [PATCH] Replace SRFI-64 with a new implementation.
Date: Mon, 21 Oct 2024 19:35:23 +0200	[thread overview]
Message-ID: <09A9A831-0334-4109-823D-71FF335EBA75@sarc.name> (raw)
In-Reply-To: <875xpmlgps.fsf@gnu.org>

I'm pleased to see all these fixes. However, I noticed a few breakages. They come from relying on undocumented behavior, but only using the public interface, so others might be affected. I don't propose to patch them, but perhaps to make a note in NEWS or (for the last two) to add a paragraph in the manual explaining how to achieve the same goal – the reference documentation doesn't have enough examples.

* test-begin and test-end now require strings. The old version accepted symbols.
* test-approximate requires real arguments. The old version accepted complex arguments.
* The exported variable test-log-to-file is gone.






  reply	other threads:[~2024-10-21 17:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 19:27 bug#73605: [PATCH] Replace SRFI-64 with a new implementation Tomas Volf
2024-10-13 20:09 ` Ludovic Courtès
     [not found] ` <87o73nrchr.fsf@gnu.org>
2024-10-20 19:24   ` Ludovic Courtès
2024-10-20 19:25   ` Ludovic Courtès
2024-10-21 17:35     ` lloda [this message]
2024-10-26 13:21       ` Ludovic Courtès
2024-10-26 14:09         ` Tomas Volf
2024-10-26 18:09           ` lloda
2024-10-21 20:15     ` Tomas Volf

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=09A9A831-0334-4109-823D-71FF335EBA75@sarc.name \
    --to=lloda@sarc.name \
    --cc=73605@debbugs.gnu.org \
    --cc=ludo@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).