public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/65230] pretty-print inconsistent output for similar objects
Date: Thu, 04 Aug 2022 18:35:35 +0000	[thread overview]
Message-ID: <bug-65230-4-lfnDI3mCCT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65230-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65230

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Ulrich Drepper from comment #3)
> Again, more uniform and I'd say it should be encouraged to use std::get
> instead of .first / .second because it's compatible with std::tuple.

Which makes sense given the even-closer alignment between them in C++23 due to
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p2165r4.pdf

(In reply to Ulrich Drepper from comment #5)
> Or should the std::pair output even be
> 
> p1 = std::pair<int,int> = {[0] = 0, [1] = 0}
> 
> ??

Yes, I think that's better.

  parent reply	other threads:[~2022-08-04 18:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27  6:46 [Bug libstdc++/65230] New: " msebor at gcc dot gnu.org
2015-02-27  8:53 ` [Bug libstdc++/65230] " redi at gcc dot gnu.org
2022-08-04 11:44 ` drepper.fsp+rhbz at gmail dot com
2022-08-04 11:47 ` drepper.fsp+rhbz at gmail dot com
2022-08-04 11:48 ` drepper.fsp+rhbz at gmail dot com
2022-08-04 11:50 ` drepper.fsp+rhbz at gmail dot com
2022-08-04 18:16 ` drepper.fsp+rhbz at gmail dot com
2022-08-04 18:35 ` redi at gcc dot gnu.org [this message]
2022-08-05 16:26 ` drepper.fsp+rhbz at gmail dot com
2022-08-05 16:27 ` drepper.fsp+rhbz at gmail dot com

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=bug-65230-4-lfnDI3mCCT@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).