Keyword arguments in procedures specified in SRFIs Lassi Kortela 21 Jul 2019 19:41 UTC
Is there a convention for what SRFI authors should do when the situation calls for a procedure with keyword arguments? Scheme doesn't have standard keyword arguments but we have the reasonably widespread foo:, :foo and #:foo syntaxes. One could always use optional arguments, but those are really unwieldy for some situations. Another option is to pass in a struct or an opaque object. This is a better option for many of the situations best addressed by keywords, but the problem then is that the SRFI has to specify more definitions so users can create and access/mutate the opaque objects. BTW, is there a dependency graph somewhere about which SRFIs depend on which other SRFIs? The only keyword SRFI seems to be Marc's SRFI 88: Keyword objects which specifies foo:. Are :foo and #:foo standardized anywhere?