unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: [nongnu] elpa/org-contrib eaef050f28: lisp/ox-bibtex.el (org-bibtex-goto-citation): Add missing require
Date: Tue, 30 Jan 2024 12:31:25 -0500	[thread overview]
Message-ID: <jwvzfwmohte.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <871q9yonl8.fsf@localhost> (Ihor Radchenko's message of "Tue, 30 Jan 2024 15:19:47 +0000")

Ihor Radchenko [2024-01-30 15:19:47] wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> The `declare-function` should be placed right next (after) the
>> `require`.  In practice it (currently) makes no difference (because of
>> technical details of how `declare-function` is (currently) implemented),
>> but in theory it clarifies that you do not intend to claim that it's safe
>> to call `obe-citations` from anywhere within `ox-bibtex`, but only from
>> within `org-bibtex-goto-citation`.
>
> Interesting.
> I am wondering if byte-compiler can somehow detect such scenarios and
> throw a warning.

In theory, if you "fix" the code as I suggested and call `obe-citations`
from outside of `org-bibtex-goto-citation`., the byte-compiler could
emit a warning.  Is that what you mean?

If you mean that the byte-compiler should warn about the current code,
it's kind of impossible: `declare-function` is specifically designed
to tell the compiler about the fact that a function is available when
the compiler doesn't know it.

IOW in order to figure out that the warning is ill-placed the compiler
would need to know how/when that function is defined, thus making
the declaration unnecessary anyway.

But yes, we could try and improve the tooling that checks those
`declare-function`s, tho currently we only provide checks to make sure
the function is indeed defined in the specified file.  We don't try
to figure out if that function will indeed be loaded/available at the
point the `declare-function` is placed (which is a much more difficult
problem).


        Stefan




  reply	other threads:[~2024-01-30 17:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <170661605561.6823.12101770977814458206@vcs2.savannah.gnu.org>
     [not found] ` <20240130120056.91DA8C0EFEF@vcs2.savannah.gnu.org>
2024-01-30 12:41   ` [nongnu] elpa/org-contrib eaef050f28: lisp/ox-bibtex.el (org-bibtex-goto-citation): Add missing require Stefan Monnier
2024-01-30 15:19     ` Ihor Radchenko
2024-01-30 17:31       ` Stefan Monnier [this message]
2024-01-30 18:59         ` Ihor Radchenko
2024-01-30 21:41           ` Stefan Monnier
2024-01-30 22:11             ` Ihor Radchenko
2024-01-30 22:57               ` Stefan Monnier
2024-01-31 14:51                 ` Emanuel Berg

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=jwvzfwmohte.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=yantar92@posteo.net \
    /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).