From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: mattiase@acm.org, 50720@debbugs.gnu.org, 50268@debbugs.gnu.org
Subject: bug#50268: 28.0.50; Assertion warning during native compilation
Date: Tue, 21 Sep 2021 19:26:19 +0300 [thread overview]
Message-ID: <83ee9hyjx0.fsf@gnu.org> (raw)
In-Reply-To: <87mto529jd.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 21 Sep 2021 18:11:34 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 50720@debbugs.gnu.org, 50268@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
> Date: Tue, 21 Sep 2021 18:11:34 +0200
>
> Mattias Engdegård <mattiase@acm.org> writes:
>
> > Now, either we fix this bug or we stop pretending that unnamed &rest
> > arguments work at all and signal an error, because it's clear from the
> > above that they can't have seen much use.
>
> I did a quick grep through core and GNU ELPA, and I couldn't find any
> instances of it being used, so I'd be fine with either solution (i.e.,
> either fixing the bug or signalling an error).
>
> Perhaps Eli has an opinion (added to the CCs).
I think I'd like to at least see the prototype of the fix to have an
opinion.
next prev parent reply other threads:[~2021-09-21 16:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 11:15 bug#50720: unnamed &rest broken Mattias Engdegård
2021-09-21 16:11 ` bug#50720: bug#50268: 28.0.50; Assertion warning during native compilation Lars Ingebrigtsen
2021-09-21 16:22 ` Mattias Engdegård
2021-09-21 17:09 ` Noam Postavsky
2021-09-21 17:53 ` Eli Zaretskii
2021-09-21 19:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-22 5:43 ` Eli Zaretskii
2021-09-23 1:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-23 6:38 ` Eli Zaretskii
2021-09-23 11:09 ` Mattias Engdegård
2021-09-23 21:03 ` Lars Ingebrigtsen
2021-09-24 6:07 ` Eli Zaretskii
2021-09-25 0:51 ` Lars Ingebrigtsen
2021-09-25 18:37 ` Mattias Engdegård
2021-09-21 16:26 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-30 14:05 Michael Welsh Duggan
2021-09-04 14:00 ` Michael Welsh Duggan
2021-09-05 15:31 ` Michael Welsh Duggan
2021-09-20 22:12 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-21 7:50 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-21 12:17 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-21 15:56 ` Andrea Corallo 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
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=83ee9hyjx0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50268@debbugs.gnu.org \
--cc=50720@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.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).