From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: Something weird with when-let*/if-let*
Date: Sat, 14 Oct 2017 22:03:16 +0200 [thread overview]
Message-ID: <8760bh1oqj.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAM-tV-8xuWtBUvLCuZuMOXCthTBLWvxOsPdqQugoSXNRzoktGg@mail.gmail.com
Noam Postavsky <npostavs@users.sourceforge.net> writes:
> On Sat, Oct 14, 2017 at 3:13 PM, Eric Abrahamsen
> <eric@ericabrahamsen.net> wrote:
>
>> This sounds pretty likely. What actually determines the order of
>> compilation, btw? I can see how the chain of requires spreads out, but I
>> don't know where it starts.
>
> I believe the order of compilation is determined only by 'make'; the
> requires only tell the compiler to load the elc or el file, not
> compile it (and note that a require inside an (eval-when-compile ...)
> form will not appear in the elc file).
Thanks, that's really useful information. So even doing (require
'message) in nnimap.el wouldn't allow us to benefit from the
eval-when-compile load of subr-x in message.el.
Besides message.el, nnimap.el is the only gnus lib to use when-let*. I
can just add another subr-x require in nnimap for now -- if it starts
getting used in more places, I guess we can require subr-x
unconditionally in gnus.el.
Thanks,
Eric
next prev parent reply other threads:[~2017-10-14 20:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 12:10 Something weird with when-let*/if-let* Eric Abrahamsen
2017-10-14 13:10 ` Noam Postavsky
2017-10-14 13:12 ` Eric Abrahamsen
2017-10-14 13:47 ` Noam Postavsky
2017-10-14 13:49 ` Noam Postavsky
2017-10-14 19:13 ` Eric Abrahamsen
2017-10-14 19:55 ` Noam Postavsky
2017-10-14 20:03 ` Eric Abrahamsen [this message]
2017-10-14 20:05 ` Eric Abrahamsen
2017-10-14 20:42 ` Stefan Monnier
2017-10-16 3:23 ` Eric Abrahamsen
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=8760bh1oqj.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 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.