public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Lancelot SIX <lsix@lancelotsix.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb::array_view slicing/container selftest - test std::array too (Re: [PATCH v2 2/2] Improve gdb::array_view ctor from contiguous containers)
Date: Tue, 9 Nov 2021 22:48:15 +0000	[thread overview]
Message-ID: <0ba86bea-3079-0b93-ad5f-4af5119695df@palves.net> (raw)
In-Reply-To: <20211109215848.h3caszzxf4lztjq7@ubuntu.lan>

On 2021-11-09 21:58, Lancelot SIX wrote:
> On Tue, Nov 09, 2021 at 05:52:20PM +0000, Pedro Alves wrote:

>> Thanks.  Looking again, I noticed we don't exercise construction from std::array containers,
>> unlike other tests.  This adds it.  WDYT?
> 
> Hi,
> 
> Actually my first version used a fixed size std::array exactly as you
> have here.  I went for a std::vector instead in the version I have
> submitted to the list so I still test against one of the standard
> containers while not having to define StdArray1.
> 
> I am absolutely fine including a test with a std::array. It could even
> replace the std::vector based test since this test is the only one that
> uses this container (in which case the '#include <vector>' line could
> also be dropped).
> 
> In the end, both options check that the old erroneous behavior that
> used to allow slicing now fails to compile. This is the most important
> point.

The main advantage that I was thinking is that testing more than one
standard container here ensures that we're not baking in some assumption
in the interface (now and forever) that only holds true for std::vector.

I'll merge the patch.

Thanks,
Pedro Alves

      reply	other threads:[~2021-11-09 22:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 20:05 [PATCH 0/2] Improve constraints on gdb::array_view::array_view Lancelot SIX
2021-10-20 20:05 ` [PATCH 1/2] Add a const version of gdb_argv:as_array_view Lancelot SIX
2021-10-30  2:03   ` Simon Marchi
2021-10-20 20:05 ` [PATCH 2/2] Improve gdb::array_view ctor from contiguous containers Lancelot SIX
2021-10-30  2:09   ` Simon Marchi
2021-11-02 14:10     ` Tom Tromey
2021-11-02 16:00   ` Pedro Alves
2021-11-02 22:51     ` Lancelot SIX
2021-11-03 22:20     ` [PATCH v2 " Lancelot SIX
2021-11-04 13:04       ` Pedro Alves
2021-11-08 23:02         ` Lancelot SIX
2021-11-09 17:52           ` [PATCH] gdb::array_view slicing/container selftest - test std::array too (Re: [PATCH v2 2/2] Improve gdb::array_view ctor from contiguous containers) Pedro Alves
2021-11-09 21:58             ` Lancelot SIX
2021-11-09 22:48               ` Pedro Alves [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=0ba86bea-3079-0b93-ad5f-4af5119695df@palves.net \
    --to=pedro@palves.net \
    --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).