Re: yeRemoving program-arities export

Skyler Ferris via "Developers list for Guile, the GNU extensibility library" <[email protected]> Wed, 15 Jan 2025 08:44:51 +0000

Newsgroups	gmane.lisp.guile.devel
Message-ID	<oFYAm1iJyiiXfSWKW47X3lNTxU9CZlcxcC1i1r0x86qZ_WRQgHYANIZACJ2IeNbLr3xAYRqLQ9WsTVobX-MRsOrzeii-eq1FElgp6DvNg7I=@skyler-ferris.me>

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)