From: Alan Mackenzie <acm@muc.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 51092@debbugs.gnu.org, acm@muc.de, Evan Klitzke <evan@eklitzke.org>
Subject: bug#51092: [PATCH] Recognize consteval and constinit modifiers in C++
Date: Tue, 12 Oct 2021 10:54:00 +0000 [thread overview]
Message-ID: <YWVpSEsVSsTESbOC@ACM> (raw)
In-Reply-To: <8735pbrd91.fsf@gnus.org>
Hello, Evan and Lars.
On Fri, Oct 08, 2021 at 13:02:02 +0200, Lars Ingebrigtsen wrote:
> Evan Klitzke <evan@eklitzke.org> writes:
> > These two modifiers were introduced by C++20. The change is trivial
> > but I tested it locally on some code I have that uses these modifiers
> > and with this change the keywords are recognized as expected. I agree
> > to copyright assignment to the FSF, etc. Patch against master is
> > attached; I think this should be backported to the emacs-28 branch as
> > well.
> [...]
> > - c++ (append '("constexpr" "explicit" "friend" "mutable" "template"
> > - "thread_local" "virtual")
> > + c++ (append '("consteval" "constexpr" "constinit" "explicit"
> > + "friend" "mutable" "template" "thread_local" "virtual")
> Makes sense to me; perhaps Alan has some comments, so I've added him to
> the CCs.
As the maintainer of CC Mode, i'm in two minds over this. It's clearly
a step in the right direction. But there's a non-trivial amount of work
to be done to implement C++20's new features, and having just those few
new keywords and nothing else in the release branch might jar.
Evan, you've clearly burrowed a fair way into CC Mode, and have some
idea of how complicated it is. Do you perhaps feel able and willing to
add a larger part of C++20's new feature set to CC Mode? Regular
discussion and help from me would, of course, be available. I envisage
starting off in the CC Mode standalone project, and transferring the new
features steadily to the Emacs master branch as they become ready; this
has been my standard way of working for many years. The standalone
project is at SourceForge, and uses Mercurial (which is easy to learn)
rather than git.
The copyright assignments are a bit of a hassle. I think they've still
got to be done on paper. But for just the patch you've proposed, an
assignment wouldn't be needed. Richard Stallman has confirmed that the
measure is the number of lines of code added/changed, not the degree of
functionality. Lars is probably better informed than me about this, and
Eli Zaretskii certainly is.
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2021-10-12 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 1:10 bug#51092: [PATCH] Recognize consteval and constinit modifiers in C++ Evan Klitzke
2021-10-08 11:02 ` Lars Ingebrigtsen
2021-10-12 10:54 ` Alan Mackenzie [this message]
2021-10-12 14:13 ` Eli Zaretskii
2021-10-14 18:22 ` Evan Klitzke
2022-09-10 5:19 ` Lars Ingebrigtsen
2022-09-13 17:26 ` Alan Mackenzie
2022-09-14 12:32 ` Lars Ingebrigtsen
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=YWVpSEsVSsTESbOC@ACM \
--to=acm@muc.de \
--cc=51092@debbugs.gnu.org \
--cc=evan@eklitzke.org \
--cc=larsi@gnus.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).