From: Pedro Alves <pedro@palves.net>
To: Matthieu Longo <matthieu.longo@arm.com>, gdb-patches@sourceware.org
Cc: Luis Machado <luis.machado@amd.com>,
Luis Machado <luis.machado.foss@gmail.com>,
Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH v1 4/8] gdb support: add index_type to array_view for documentation purpose
Date: Fri, 3 Jul 2026 20:55:34 +0100 [thread overview]
Message-ID: <90d5b118-fa2a-4c6e-91c3-48bd9deaf27f@palves.net> (raw)
In-Reply-To: <20260703185853.450440-5-matthieu.longo@arm.com>
On 2026-07-03 19:58, Matthieu Longo wrote:
> The semantic of slice (size_type start, size_type size) might be
> slightly ambiguous if the variable names are omitted. Making the
> index type different from the size type removes this ambiguity.
> This change is purely cosmetic.
You've changed the type from size_t (unsigned) to ptrdiff_t (signed). That's not cosmetic.
The code was using size_type (and size_t) for indexing, as that's what standard containers
use. There's no std::vector::index_type, etc.
Also this:
> -void copy (gdb::array_view<U> src, gdb::array_view<T> dest)
> +void copy (array_view<U> src, array_view<T> dest)
... seem unrelated.
next prev parent reply other threads:[~2026-07-03 19:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 18:58 [PATCH v1 0/8] gdb: various refactoring in linux-tdep Matthieu Longo
2026-07-03 18:58 ` [PATCH v1 1/8] gdb/linux-tdep: use pid_t consistently for process IDs Matthieu Longo
2026-07-05 21:22 ` Tom Tromey
2026-07-06 9:30 ` Matthieu Longo
2026-07-03 18:58 ` [PATCH v1 2/8] gdb/linux-tdep: change linux_fill_prpsinfo to return bool Matthieu Longo
2026-07-03 18:58 ` [PATCH v1 3/8] target_fileio_read_stralloc: add an optional length parameter Matthieu Longo
2026-07-03 18:58 ` [PATCH v1 4/8] gdb support: add index_type to array_view for documentation purpose Matthieu Longo
2026-07-03 19:55 ` Pedro Alves [this message]
2026-07-06 10:51 ` Matthieu Longo
2026-07-03 18:58 ` [PATCH v1 5/8] gdb support: add gdb::replace algorithm for iterators and ranges Matthieu Longo
2026-07-03 18:58 ` [PATCH v1 6/8] gdb: introduce helper class file_reader_t Matthieu Longo
2026-07-03 18:58 ` [PATCH v1 7/8] gdb/linux-tdep: parse ProtectionKey in /proc/PID/smaps Matthieu Longo
2026-07-03 18:58 ` [PATCH v1 8/8] gdb/linux: add helpers to read AT_HWCAP3 Matthieu Longo
2026-07-07 10:39 ` Yury Khrustalev
2026-07-07 15:51 ` Matthieu Longo
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=90d5b118-fa2a-4c6e-91c3-48bd9deaf27f@palves.net \
--to=pedro@palves.net \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado.foss@gmail.com \
--cc=luis.machado@amd.com \
--cc=matthieu.longo@arm.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