From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <pedro@palves.net>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/7] More C++17 Updates
Date: Thu, 19 Oct 2023 14:26:44 -0600 [thread overview]
Message-ID: <87msweuznf.fsf@tromey.com> (raw)
In-Reply-To: <13d8b3d7-f1e5-41ad-b1dc-d1be245158c6@palves.net> (Pedro Alves's message of "Tue, 17 Oct 2023 10:06:59 +0100")
>> Let me know what you think.
Pedro> Other than the comment on the try_emplace patch, this all LGTM:
Pedro> Approved-By: Pedro Alves <pedro@palves.net>
Thanks.
I added one more patch that I'll send in v2: I realized we can remove
gdb_static_assert now.
Tom
prev parent reply other threads:[~2023-10-19 20:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 23:02 Tom Tromey
2023-10-16 23:02 ` [PATCH 1/7] Use C++17 [[fallthrough]] attribute Tom Tromey
2023-10-16 23:17 ` John Baldwin
2023-10-19 20:23 ` Tom Tromey
2023-10-17 8:53 ` Luis Machado
2023-10-19 20:23 ` Tom Tromey
2023-10-16 23:02 ` [PATCH 2/7] Switch to -Wimplicit-fallthrough=5 Tom Tromey
2023-10-16 23:02 ` [PATCH 3/7] Enable some C++14 code in array-view.h Tom Tromey
2023-10-16 23:02 ` [PATCH 4/7] Use try_emplace in index-write.c Tom Tromey
2023-10-17 8:56 ` Pedro Alves
2023-10-17 9:30 ` Lancelot SIX
2023-10-19 20:24 ` Tom Tromey
2023-10-16 23:02 ` [PATCH 5/7] Rely on C++17 <new> in new-op.cc Tom Tromey
2023-10-16 23:02 ` [PATCH 6/7] Rely on copy elision in scope-exit.h Tom Tromey
2023-10-16 23:02 ` [PATCH 7/7] Use C++17 void_t Tom Tromey
2023-10-17 9:06 ` [PATCH 0/7] More C++17 Updates Pedro Alves
2023-10-19 20:26 ` Tom Tromey [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87msweuznf.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox