public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Lancelot SIX <Lancelot.Six@amd.com>
To: Pedro Alves <pedro@palves.net>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 06/11] gdb: Use std::string_view instead of gdb::string_view
Date: Tue, 17 Oct 2023 15:13:07 +0100	[thread overview]
Message-ID: <b179b31c-d24a-4034-b75d-5e0957848cfc@amd.com> (raw)
In-Reply-To: <fb5aa9ae-a80b-4206-a180-3ad9d4e9e764@palves.net>

Hi,

On 16/10/2023 22:51, Pedro Alves wrote:

>> Lancelot> +         std::string_view name;
>> Lancelot> +         if (const char *name_str = keyname (ch);
>> Lancelot> +             name_str != nullptr)
>>
>> We should probably discuss whether to allow this construct before
>> letting it in.
>>
>> Personally I'm ok with it.
> 
> I think it may look a little weird if you're not used to it (like I am not), but
> OTOH it isn't really different from introducing a variable to scope with "for", like:
> 
>   for (const char *name_str = keyname (ch);
>        name_str != nullptr; ....)
>     ....
> 
> so I suspect we'll all just get used to it and think nothing of it in a few years.
> 
> So am I fine with it too.
> 

I don't mind not using this for now.  The "name_str" will be declared 
outside of the if scope for now.

If this construct is comes in, there will also be the question of coding 
style (i.e. single line if line length permits or multiple lines as 
I did here).  I guess we could go the same way we do for "for" and 
prefer single line.

Best,
Lancelot.

  reply	other threads:[~2023-10-17 14:13 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 14:44 [PATCH 00/11] GDB: Require C++17 Lancelot Six
2023-10-13 14:44 ` [PATCH 01/11] gdb/ax_cxx_compile_stdcxx.m4: upgrade Lancelot Six
2023-10-13 14:44 ` [PATCH 02/11] gdb/gdbsupport/gdbserver: Require c++17 Lancelot Six
2023-10-13 15:21   ` Eli Zaretskii
2023-10-16 21:50   ` Pedro Alves
2023-10-13 14:44 ` [PATCH 03/11] gdb: Use C++17's std::make_unique instead of gdb::make_unique Lancelot Six
2023-10-16 19:14   ` Tom Tromey
2023-10-17 14:02     ` Lancelot SIX
2023-10-13 14:44 ` [PATCH 04/11] gdb: Replace gdb::optional with std::optional Lancelot Six
2023-10-13 14:44 ` [PATCH 05/11] gdbsupport: remove gdb::optional Lancelot Six
2023-10-13 14:44 ` [PATCH 06/11] gdb: Use std::string_view instead of gdb::string_view Lancelot Six
2023-10-14 21:50   ` Tom Tromey
2023-10-14 23:58     ` Six, Lancelot
2023-10-16 15:06     ` Lancelot SIX
2023-10-16 19:35       ` Tom Tromey
2023-10-16 21:51         ` Pedro Alves
2023-10-17 14:13           ` Lancelot SIX [this message]
2023-10-17 14:20             ` Simon Marchi
2023-10-13 14:44 ` [PATCH 07/11] gdb: Remove uses of gdb::to_string (const std::string_view &) Lancelot Six
2023-10-13 14:44 ` [PATCH 08/11] gdbsupport: Remove gdb::string_view Lancelot Six
2023-10-16 19:38   ` Tom Tromey
2023-10-13 14:44 ` [PATCH 09/11] gdbsupport: Replace gdb::invoke_result with std::invoke_result Lancelot Six
2023-10-13 14:44 ` [PATCH 10/11] gdb/disasm.h: Mark callbacks noexcept unconditionally Lancelot Six
2023-10-16 21:51   ` Pedro Alves
2023-10-13 14:44 ` [PATCH 11/11] gdb: Use initializers in lambda captures unconditionally Lancelot Six
2023-10-16 19:43 ` [PATCH 00/11] GDB: Require C++17 Tom Tromey
2023-10-16 21:53   ` Pedro Alves
2023-10-23 13:42     ` Lancelot SIX
2023-10-28 20:48       ` Lancelot SIX
2023-11-21 12:04         ` [COMMITTED PATCH v2 0/9] " Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 1/9] gdb: Use C++17's std::make_unique instead of gdb::make_unique Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 2/9] gdb: Replace gdb::optional with std::optional Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 3/9] gdbsupport: remove gdb::optional Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 4/9] gdb: Use std::string_view instead of gdb::string_view Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 5/9] gdb: Remove uses of gdb::to_string (const std::string_view &) Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 6/9] gdbsupport: Remove gdb::string_view Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 7/9] gdbsupport: Replace gdb::invoke_result with std::invoke_result Lancelot Six
2023-11-21 12:04         ` [COMMITTED PATCH v2 8/9] gdb/disasm.h: Mark callbacks noexcept unconditionally Lancelot Six
2023-11-21 12:05         ` [COMMITTED PATCH v2 9/9] gdb: Use initializers in lambda captures unconditionally Lancelot Six

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=b179b31c-d24a-4034-b75d-5e0957848cfc@amd.com \
    --to=lancelot.six@amd.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    --cc=tom@tromey.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).