From: Maxime Devos <maximedevos@telenet.be>
To: Skyler <skyvine@protonmail.com>,
"guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: RE: Removing program-arities export
Date: Sun, 5 Jan 2025 19:07:25 +0100 [thread overview]
Message-ID: <20250105190726.xW7S2D00948vBLV06W7S96@albert.telenet-ops.be> (raw)
In-Reply-To: <WZp-Z-HhbASpn9zmycHpyPermX68RQKZqs5PKrA0-UjcfEhjaZJm7Y6ZjMxsxVoUlUMMz60Eq3IYuOV3cc4CaGPVDiZfLtqpStMBHuRP1GQ=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
>It is only used in the `program-arity function`, which is not called anywhere in the Guile repository (and calling it with valid inputs results in an error due to the `program-arities` being undefined).
This is untrue, it (i.e. program-arities) is also used in the manual.
>Removing those functions is simple, but the `arity:` accessors have more users, […]
It shouldn’t be removed, rather a replacement should be provided somewhere.
Regardless of the changes to the VM, compiled procedures still exist, and by definition that’s what a ‘program’ is, so ‘programs’ still exist, and hence many of the procedures in that module still make sense, including program-arities. In particular, arity information is still recorded (in .guile.arities), so it should be made / kept accessible somewhere.
Best regards,
Maxime Devos
[-- Attachment #2: Type: text/html, Size: 2333 bytes --]
next prev parent reply other threads:[~2025-01-05 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-29 11:16 Removing program-arities export Skyler via Developers list for Guile, the GNU extensibility library
2025-01-05 18:07 ` Maxime Devos [this message]
2025-01-06 11:01 ` Skyler via Developers list for Guile, the GNU extensibility library
2025-01-08 11:23 ` Skyler Ferris via Developers list for Guile, the GNU extensibility library
2025-01-08 20:21 ` yeRemoving " Dr. Arne Babenhauserheide
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=20250105190726.xW7S2D00948vBLV06W7S96@albert.telenet-ops.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=skyvine@protonmail.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).