Email list hosting service & mailing list manager

New draft (#2) of SRFI 212: Aliases Arthur A. Gleckler (30 Jan 2021 22:23 UTC)
Re: New draft (#2) of SRFI 212: Aliases John Cowan (30 Jan 2021 22:47 UTC)
Re: New draft (#2) of SRFI 212: Aliases Lassi Kortela (30 Jan 2021 23:08 UTC)
Re: New draft (#2) of SRFI 212: Aliases Marc Nieper-Wißkirchen (31 Jan 2021 08:56 UTC)
Re: New draft (#2) of SRFI 212: Aliases Marc Nieper-Wißkirchen (31 Jan 2021 08:55 UTC)
Re: New draft (#2) of SRFI 212: Aliases Lassi Kortela (31 Jan 2021 09:10 UTC)
Re: New draft (#2) of SRFI 212: Aliases Marc Nieper-Wißkirchen (31 Jan 2021 09:22 UTC)
Re: New draft (#2) of SRFI 212: Aliases Per Bothner (31 Jan 2021 10:47 UTC)
Re: New draft (#2) of SRFI 212: Aliases Marc Nieper-Wißkirchen (31 Jan 2021 12:39 UTC)
Re: New draft (#2) of SRFI 212: Aliases Per Bothner (31 Jan 2021 17:04 UTC)
Re: New draft (#2) of SRFI 212: Aliases Marc Nieper-Wißkirchen (31 Jan 2021 17:35 UTC)

Re: New draft (#2) of SRFI 212: Aliases Lassi Kortela 31 Jan 2021 09:09 UTC

> As described in the SRFI, the define-XXX forms introduce new bindings
> (locations, keywords, etc.). Contrary to those, alias doesn't. This is
> one reason why it is called `alias` and not `define-alias`. Note that
> this SRFI in principle allows an implementation to alias an unbound
> identifier (it is left unspecified), in which case not even a "new
> identifier is introduced" (whatever this means).

I'm convinced by your reasoning. `alias` is the right name after all.