From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 12299@debbugs.gnu.org, Roland Winkler <winkler@gnu.org>
Subject: bug#12299: 24.1; no byte compiler warning for inline function call with too few arguments
Date: Sat, 17 Jul 2021 16:04:49 +0200 [thread overview]
Message-ID: <871r7x6npa.fsf@gnus.org> (raw)
In-Reply-To: <jwvmtqmjmkv.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 16 Jul 2021 11:39:46 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> No particular comments, no. IIRC this part of the byte compiler is just
> not making efforts to detect such errors, indeed.
> It's probably not hard to fix.
Right. Well, let's hope that somebody feels up to poking at this
problem.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-07-17 14:04 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 [this message]
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
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=871r7x6npa.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=12299@debbugs.gnu.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 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.