From: Taylan Kammer <taylan.kammer@gmail.com>
To: 40294@debbugs.gnu.org, John Cowan <cowan@ccil.org>
Subject: bug#40294: Documentation for arity procedures doesn't match behavior
Date: Sun, 16 May 2021 17:26:12 +0200 [thread overview]
Message-ID: <80122408-c057-c81c-dfe7-9afa7600854e@gmail.com> (raw)
In-Reply-To: <b94847aa-f32f-0d7a-f727-0d446e3e489d@gmail.com>
On 16.05.2021 02:07, Taylan Kammer wrote:
>
> Will investigate more tomorrow.
>
It seems that commit 1c33be992e8120abd20add8021e4d91d226f5b6a removed
much of the programs API at the C level but forgot to make the changes
to the corresponding Scheme module. (It was a big commit, part of
changing the whole VM implementation.)
I wonder if anyone really uses the program API. It might be best to
deprecate it in favor of an improved procedure metadata API.
--
Taylan
prev parent reply other threads:[~2021-05-16 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 21:42 bug#40294: Documentation for arity procedures doesn't match behavior John Cowan
2021-05-16 0:07 ` Taylan Kammer
2021-05-16 15:26 ` Taylan Kammer [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=80122408-c057-c81c-dfe7-9afa7600854e@gmail.com \
--to=taylan.kammer@gmail.com \
--cc=40294@debbugs.gnu.org \
--cc=cowan@ccil.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).