unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
Subject: Re: *-loaddefs.el files are not byte-compiled after being regenerated
Date: Thu, 04 Aug 2022 18:41:26 -0400	[thread overview]
Message-ID: <jwvr11v4ott.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87edxvd4ru.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 05 Aug 2022 00:26:29 +0200")

Lars Ingebrigtsen [2022-08-05 00:26:29] wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Why do we compile those?  I thought we only wanted to compile
>> `lisp/loaddefs.el`.
>
> To make
>
> ;;;###foo-autoload
> (progn
>   (defun foo ()
>     (here's a big bunch of code)))
>
> byte-compiled.

Ah, I thought the change was only about the handling of docstrings for
`etc/DOC`, but indeed there are other benefits to byte-compiling
loaddefs files.  Not sure they're important enough, tho (we still don't
compile ELPA packages's autoloads, IIUC).


        Stefan




  reply	other threads:[~2022-08-04 22:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 16:49 *-loaddefs.el files are not byte-compiled after being regenerated Eli Zaretskii
2022-08-04 16:53 ` Lars Ingebrigtsen
2022-08-04 16:56   ` Lars Ingebrigtsen
2022-08-04 17:10     ` Lars Ingebrigtsen
2022-08-04 17:22       ` Eli Zaretskii
2022-08-04 17:18   ` Eli Zaretskii
2022-08-04 22:13     ` Stefan Monnier
2022-08-04 22:26       ` Lars Ingebrigtsen
2022-08-04 22:41         ` Stefan Monnier [this message]
2022-08-04 22:47           ` Lars Ingebrigtsen
2022-08-04 22:56             ` Stefan Monnier
2022-08-05 11:52               ` 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=jwvr11v4ott.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).