From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 12299@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
Roland Winkler <winkler@gnu.org>
Subject: bug#12299: 24.1; no byte compiler warning for inline function call with too few arguments [PATCH]
Date: Fri, 23 Jul 2021 12:21:28 -0400 [thread overview]
Message-ID: <jwv5yx1rogb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E35B5647-EFEB-4A3F-B97A-F5FF1C9F53E4@acm.org> ("Mattias Engdegård"'s message of "Fri, 23 Jul 2021 17:52:41 +0200")
>> IOW I think we want that `byte-compile--check-arity-bytecode` call to be
>> elsewhere (in the code that actually compiles the code constructed by
>> `(,fn ,@(cdr form))).
> Tried that first, but then we no longer have the function name so the user sees
> Warning: ‹bytecode gibberish› called with 1 argument but requires 2
Ah, right, makes sense, thanks,
Stefan
prev parent reply other threads:[~2021-07-23 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 2:14 bug#12299: 24.1; no byte compiler warning for inline function call with too few arguments Roland Winkler
2019-08-16 22:46 ` Lars Ingebrigtsen
2021-07-15 20:29 ` Lars Ingebrigtsen
2021-07-16 15:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-17 14:04 ` Lars Ingebrigtsen
2021-07-22 13:14 ` bug#12299: 24.1; no byte compiler warning for inline function call with too few arguments [PATCH] Mattias Engdegård
2021-07-23 11:09 ` Lars Ingebrigtsen
2021-07-23 13:18 ` Mattias Engdegård
2021-12-06 23:36 ` bug#12299: 24.1; no byte compiler warning for inline function call with too few arguments Stefan Kangas
2021-07-23 15:02 ` bug#12299: 24.1; no byte compiler warning for inline function call with too few arguments [PATCH] Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-23 15:52 ` Mattias Engdegård
2021-07-23 16:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=jwv5yx1rogb.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=12299@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
--cc=monnier@iro.umontreal.ca \
--cc=winkler@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 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).