From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: Lancelot SIX <lsix@lancelotsix.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/5] Rewrite final cleanups
Date: Tue, 27 Feb 2024 10:36:26 -0700 [thread overview]
Message-ID: <87a5nlvmg5.fsf@tromey.com> (raw)
In-Reply-To: <87edcxvmul.fsf@tromey.com> (Tom Tromey's message of "Tue, 27 Feb 2024 10:27:46 -0700")
Tom> ... and also a C++17 meta-bug, and various C++17 to-do items I've
Tom> thought of in the past.
... wanted to add on to this.
I think Simon had some other ideas in this space, though I don't recall
them offhand & couldn't easily find them.
My notes say that I thought we could use CTAD somewhere, but I couldn't
find the spot I was thinking of. Also we could use the [[maybe_unused]]
or [[nodiscard]] attributes. I didn't file bugs for these but I suppose
I could... somehow they seemed less well-defined as tasks to me, like
when would we know they were done.
Finally, I also looked at using std::invoke in expop.h, but it doesn't
seem like it would really simplify the code that much.
Tom
next prev parent reply other threads:[~2024-02-27 17:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 21:11 [PATCH 0/5] Restore DAP 'quit' request Tom Tromey
2024-02-23 21:11 ` [PATCH 1/5] Rewrite final cleanups Tom Tromey
2024-02-25 22:30 ` Lancelot SIX
2024-02-26 18:53 ` Tom Tromey
2024-02-27 14:03 ` Lancelot SIX
2024-02-27 17:27 ` Tom Tromey
2024-02-27 17:36 ` Tom Tromey [this message]
2024-03-03 16:50 ` Lancelot SIX
2024-02-23 21:11 ` [PATCH 2/5] Add extension_language_ops::shutdown Tom Tromey
2024-02-23 21:11 ` [PATCH 3/5] Change finalize_values into a final cleanup Tom Tromey
2024-02-23 21:11 ` [PATCH 4/5] Add final cleanup for runnables Tom Tromey
2024-02-23 21:11 ` [PATCH 5/5] Explicitly quit gdb from DAP server thread Tom Tromey
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=87a5nlvmg5.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).