unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: master c8a2af3037 1/3: Add new function function-alias-p
Date: Fri, 14 Jan 2022 08:28:35 +0100	[thread overview]
Message-ID: <877db2vkrg.fsf@gnus.org> (raw)
In-Reply-To: <jwvzgnztzny.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 13 Jan 2022 10:39:20 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Hmm... would it make sense to return `(b c . <foo>)` where <foo> is the
> "last, non-symbol, value", i.e. (symbol-function 'c)?
>
> It seems in most cases where we'd use `function-alias-p` we want to
> follow the trail of aliases and then do something on the final
> non-alias definition.

In the two use cases I had here, one wanted to have the final symbol
(for *Help*) and the other wanted to have all the symbols (to check
symbol properties).

An the semantics would be kinda odd -- in the non-alias case, we'd still
return nil, right?  So the user still has to use symbol-function on
something, so I think the current definition (stop at the last symbol)
is the one that's more practical.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2022-01-14  7:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164206376686.342.13318619183595442698@vcs2.savannah.gnu.org>
     [not found] ` <20220113084927.707D2C0DA30@vcs2.savannah.gnu.org>
2022-01-13 10:41   ` master c8a2af3037 1/3: Add new function function-alias-p Robert Pluim
2022-01-14  7:25     ` Lars Ingebrigtsen
2022-01-13 15:39   ` Stefan Monnier
2022-01-14  7:28     ` Lars Ingebrigtsen [this message]
2022-01-14 16:10       ` Stefan Monnier
2022-01-15  8:18         ` Lars Ingebrigtsen
2022-01-15 14:39           ` Stefan Monnier
2022-01-20  9:54             ` Lars Ingebrigtsen

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877db2vkrg.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).