unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: master b2416d2c029 4/6: Don't load comp when installing an existing trampoline
Date: Thu, 16 Nov 2023 03:35:07 -0500	[thread overview]
Message-ID: <yp134x66qpw.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvo7fwph44.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 14 Nov 2023 09:07:15 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> - The `declare-function` should be moved to right after (require
>>>   'comp-run), i.e. when we do know that the function should be available
>>>   and it will thus silence only spurious warnings.
>>
>> Ack will do, out of curiosity what is the downside of having the
>> declare-function at top level?  I thought is there to silence a compile
>> time warning (and thus the branch is inserted in should not play a
>> role).
>
> If you call that function from elsewhere in the file, there will be no
> compilation warning, even though the call may error at run time because
> `comp-run` wasn't loaded.
>
> By moving the `declare-function` you make sure only those warnings that
> you know for sure are spurious (because we just did `(require
> 'comp-run)`) will get silenced.

Thanks for the explaination, done.

>> As mentioned in the other thread I fear I don't remeber the answer to
>> those quesitons.  The best we can do is to remove the call and test
>> Emacs to find if there's still a good reason.
>
> Then let's remove it in `master`.  This way, if it's needed we'll get to
> see why/when and we'll be able to at the very least add a good comment,
> or maybe replace it with a better solution.

Ack, I'll try it before in my machine and push it if I see no
regressions here.

Thanks

  Andrea



  reply	other threads:[~2023-11-16  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <169952969842.2327.17551267288789292121@vcs2.savannah.gnu.org>
     [not found] ` <20231109113503.9890EC0C198@vcs2.savannah.gnu.org>
2023-11-13 18:46   ` master b2416d2c029 4/6: Don't load comp when installing an existing trampoline Stefan Monnier
2023-11-14  9:33     ` Andrea Corallo
2023-11-14 14:07       ` Stefan Monnier
2023-11-16  8:35         ` Andrea Corallo [this message]
2023-11-16  9:34           ` Andrea Corallo

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=yp134x66qpw.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).