unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: Using funcall on inline functions
Date: Sun, 13 Dec 2020 10:27:03 -0800	[thread overview]
Message-ID: <87czzdzhmw.fsf@ericabrahamsen.net> (raw)
In-Reply-To: jwvim95lh1d.fsf-monnier+emacs@gnu.org

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

>> Hmm, interesting. I guess I would feel a little weird about having to
>> change all callers specifically for this -- I can see myself six months
>> from now having no memory of doing this, and causing bugs for myself.
>
> Yeah, `gv-ref` is not super popular, indeed.  Can't blame you.

I actually like the mechanism and what it lets you do, but would prefer
it to be buried deep someplace where I can't see it.

>>> [ BTW, your `ebdb-add-to-list` has a bug in that it will evaluate its
>>> second argument before its first. ]
>> inline-letevals! But, for my information, isn't the bug that ELEMENT is
>> evaluated twice?
>
> Oh, yeah, that as well.
>
>> Why does the order of evaluation matter?
>
> Because in ELisp order of evaluation of function arguments is specified
> to be "left to right" and code can (and does every once in a while) rely
> on it.  It's not super-frequent, but not really rare either (e.g. it's
> quite common for things like `delete-region`).

Not something that ever occurred to me. This has been an educational
thread, even though the result will probably be me deciding this inline
isn't necessary at all.

Thanks,
Eric




      reply	other threads:[~2020-12-13 18:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-12 22:49 Using funcall on inline functions Eric Abrahamsen
2020-12-12 23:28 ` Stefan Monnier
2020-12-13 17:48   ` Eric Abrahamsen
2020-12-13 18:12     ` Stefan Monnier
2020-12-13 18:27       ` Eric Abrahamsen [this message]

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=87czzdzhmw.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-devel@gnu.org \
    /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).