unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Skyler Ferris via "Developers list for Guile, the GNU extensibility library" <guile-devel@gnu.org>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: "Skyler Ferris via \"Developers list for Guile,
	the GNU extensibility library\"" <guile-devel@gnu.org>,
	Maxime Devos <maximedevos@telenet.be>
Subject: Re: yeRemoving program-arities export
Date: Wed, 15 Jan 2025 08:44:51 +0000	[thread overview]
Message-ID: <oFYAm1iJyiiXfSWKW47X3lNTxU9CZlcxcC1i1r0x86qZ_WRQgHYANIZACJ2IeNbLr3xAYRqLQ9WsTVobX-MRsOrzeii-eq1FElgp6DvNg7I=@skyler-ferris.me> (raw)
In-Reply-To: <87ldvlawg0.fsf@web.de>

Hi again,

Can I clarify whether you raised this point as a concern in principle or if you use/maintain/are aware of a project that is currently unable to upgrade due to this problem? In the latter case, I would appreciate if you could answer the following questions (and/or pass them along to others that they might be relevant to):

1. Is it important that you are able to use this API (program-arity, program-arities) on any arbitrary function or only a specific subset of functions?

2. Do use use the arity:start and arity:end accessors? If so, could you describe what this information is being used for?

Thanks,
Skyler (they/them)



  parent reply	other threads:[~2025-01-15  8:44 UTC|newest]

Thread overview: 9+ 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
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
2025-01-09  9:53         ` Skyler Ferris via Developers list for Guile, the GNU extensibility library
2025-01-15  8:44         ` Skyler Ferris via Developers list for Guile, the GNU extensibility library [this message]
2025-01-15  9:47       ` Removing " Maxime Devos
2025-01-15 11:10         ` Skyler Ferris via Developers list for Guile, the GNU extensibility library

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='oFYAm1iJyiiXfSWKW47X3lNTxU9CZlcxcC1i1r0x86qZ_WRQgHYANIZACJ2IeNbLr3xAYRqLQ9WsTVobX-MRsOrzeii-eq1FElgp6DvNg7I=@skyler-ferris.me' \
    --to=guile-devel@gnu.org \
    --cc=arne_bab@web.de \
    --cc=dev@skyler-ferris.me \
    --cc=maximedevos@telenet.be \
    /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).