From: Jonathan Wakely <jwakely@redhat.com>
To: Philipp Fent <fent@in.tum.de>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: Add pretty printer for std::span
Date: Thu, 14 Apr 2022 16:49:27 +0100 [thread overview]
Message-ID: <CACb0b4k6e27N0rugtKvU77MefWmHd63tMwNPkQNi0ynaO1RnDw@mail.gmail.com> (raw)
In-Reply-To: <20220404105257.199452-1-fent@in.tum.de>
On Mon, 4 Apr 2022 at 11:54, Philipp Fent via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> This improves the debug output for C++20 spans.
> Before:
> {static extent = 18446744073709551615, _M_ptr = 0x7fffffffb9a8,
> _M_extent = {_M_extent_value = 2}}
> Now with StdSpanPrinter:
> std::span of length 2 = {1, 2}
prev parent reply other threads:[~2022-04-14 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 10:52 Philipp Fent
2022-04-04 11:39 ` Jonathan Wakely
2022-04-19 9:34 ` Philipp Fent
2022-04-19 10:28 ` Jonathan Wakely
2022-04-19 11:32 ` Philipp Fent
2022-04-19 11:36 ` Jonathan Wakely
2022-04-14 15:49 ` Jonathan Wakely [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=CACb0b4k6e27N0rugtKvU77MefWmHd63tMwNPkQNi0ynaO1RnDw@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=fent@in.tum.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.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.
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).