From: Juanma Barranquero <lekktu@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 13052@debbugs.gnu.org
Subject: bug#13052: 24.3.50; mention recent change of `kbd' to a function in NEWS
Date: Sun, 2 Dec 2012 03:26:45 +0100 [thread overview]
Message-ID: <CAAeL0ST0S3LKWqpTx378zdh-rZoDnhQQwuHYC73RPLYoNmUhxQ@mail.gmail.com> (raw)
In-Reply-To: <8B94F420D989475D8089DCF31ECF8EAC@us.oracle.com>
On Sun, Dec 2, 2012 at 3:18 AM, Drew Adams <drew.adams@oracle.com> wrote:
> Thanks. So I guess that means that if I have a similar (e.g., identical, for
> discussion) function and I put property `pure' on it then I will get the same
> optimization?
I think so, though I haven't really looked that much at byte-opt's code.
> What happens if someone erroneously adds that property to a function that is not
> pure but whose args all satisfy `macroexp-const-p'? Do you just lose the
> optimization or could something much worse happen?
I suppose (but again, I haven't studied the code) that some calls to
that function would likely be optimized away, which would cause
erroneous execution in case the function really does have side
effects.
> In any case, this property should be documented.
Not surprisingly, I disagree. I don't think it is intended to be used
by third-party packages. Documenting it is asking for trouble.
Juanma
next prev parent reply other threads:[~2012-12-02 2:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 0:28 bug#13052: 24.3.50; mention recent change of `kbd' to a function in NEWS Drew Adams
2012-12-02 1:52 ` Juanma Barranquero
2012-12-02 2:18 ` Drew Adams
2012-12-02 2:26 ` Juanma Barranquero [this message]
2012-12-02 3:36 ` Drew Adams
2012-12-02 3:50 ` Juanma Barranquero
2012-12-02 4:07 ` Drew Adams
2012-12-02 4:19 ` Juanma Barranquero
2012-12-02 4:50 ` Drew Adams
2012-12-02 11:33 ` Michael Heerdegen
2012-12-02 9:14 ` Chong Yidong
2012-12-02 17:13 ` Drew Adams
2012-12-06 18:02 ` Drew Adams
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=CAAeL0ST0S3LKWqpTx378zdh-rZoDnhQQwuHYC73RPLYoNmUhxQ@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=13052@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).