From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: cpitclaudel@gmail.com, emacs-devel@gnu.org, raman@google.com
Subject: Re: More reliable byte compilation, take 45
Date: Tue, 05 Oct 2021 18:41:21 +0300 [thread overview]
Message-ID: <83czoj4gym.fsf@gnu.org> (raw)
In-Reply-To: <jwvsfxf7gon.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 05 Oct 2021 09:27:24 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: raman@google.com, cpitclaudel@gmail.com, emacs-devel@gnu.org
> Date: Tue, 05 Oct 2021 09:27:24 -0400
>
> > And that's all? Then why not fix that problem right away, it sounds
> > like something that should be easy to fix. (Though I'm not sure I
> > understand why "some other ELisp file was not loaded beforehand" -- is
> > that a case of a missing 'require' or 'eval-when-compile' or somesuch?)
>
> Often the problem is with packages where you basically have to load
> all/most the files before you can call any of its functions (because of
> mutual dependencies between the files) and where the authors never
> compile the code or only ever compile the code from a running session
> where the files have already been loaded.
Wouldn't local no-native-compile be the proper solutions for those
files?
next prev parent reply other threads:[~2021-10-05 15:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 10:51 More reliable byte compilation, take 45 Lars Ingebrigtsen
2021-10-04 15:36 ` Clément Pit-Claudel
2021-10-04 16:16 ` Lars Ingebrigtsen
2021-10-04 18:16 ` T.V Raman
2021-10-04 18:21 ` Eli Zaretskii
2021-10-04 19:18 ` Stefan Monnier
2021-10-04 19:51 ` Eli Zaretskii
2021-10-04 20:13 ` Stefan Monnier
2021-10-05 11:52 ` Eli Zaretskii
2021-10-05 13:27 ` Stefan Monnier
2021-10-05 14:06 ` Adam Porter
2021-10-05 15:41 ` Eli Zaretskii [this message]
2021-10-04 16:03 ` Steingold
2021-10-04 17:35 ` Lars Ingebrigtsen
2021-10-04 18:59 ` Steingold
2021-10-05 7:14 ` Lars Ingebrigtsen
2021-10-05 14:50 ` Steingold
2021-10-05 14:51 ` Steingold
2021-10-05 19:30 ` Stefan Monnier
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=83czoj4gym.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=raman@google.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).