From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juanma Barranquero'" <lekktu@gmail.com>
Cc: 13052@debbugs.gnu.org
Subject: bug#13052: 24.3.50; mention recent change of `kbd' to a function in NEWS
Date: Sat, 1 Dec 2012 20:07:08 -0800 [thread overview]
Message-ID: <1912812BDF6B490FAA156D879299DD7C@us.oracle.com> (raw)
In-Reply-To: <CAAeL0STnEL54xyU87xKSJcNjJXpUE4qhgRZeUJs4ZqW3oVT6Jw@mail.gmail.com>
> > Why? What makes it special?
>
> Do you really think that there are many things in byte-opt.el intended
> for third-party packages? The only reference to it in the docs is in
> Writing Emacs Primitives, which is not exactly lisp-level stuff.
The application of property `pure' to `kbd' is not in byte-opt.el. It is in
subr.el. And in my code it would, likewise, be in an ordinary Lisp library.
I was just asking whether you know of something that makes this special to Emacs
Dev and not appropriate for user libraries. If you don't know of anything,
fine; perhaps someone else does.
It is a question: whether `pure' is information that users can reasonably use to
inform the byte compiler that a function is what the compiler would expect of a
pure function, i.e., what the code you pointed me to would expect, in order to
be able to perform that particular optimization.
next prev parent reply other threads:[~2012-12-02 4:07 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
2012-12-02 3:36 ` Drew Adams
2012-12-02 3:50 ` Juanma Barranquero
2012-12-02 4:07 ` Drew Adams [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1912812BDF6B490FAA156D879299DD7C@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=13052@debbugs.gnu.org \
--cc=lekktu@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.