public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: "François Dumont" <frs.dumont@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>, cauldwell.thomas@gmail.com
Cc: libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: string::find(string_view) is missing from <debug/string>
Date: Thu, 30 Jun 2022 06:36:01 +0200	[thread overview]
Message-ID: <28ef4daf-20c0-0e14-f4f0-5a53397bff88@gmail.com> (raw)
In-Reply-To: <CACb0b4m0j2Q+k_NSyWWzwhE-YEzey6RFLfC4Vhod0BHHwRxHFg@mail.gmail.com>

On 24/06/22 12:07, Jonathan Wakely via Libstdc++ wrote:
> On Fri, 24 Jun 2022 at 08:45, Frederick Virchanza Gotham via Libstdc++
> <libstdc++@gcc.gnu.org> wrote:
>> I was hoping to replace "std::string" with "__gnu_debug::string" in my
>> program, but when I do so, it no longer compiles.
>>
>> It fails to compile because "__gnu_debug::string" is missing the
>> member function:
>>
>>      template <class StringViewLike>
>>      constexpr size_type find( StringViewLike const &t, size_type pos =
>> 0u ) const noexcept;
>>
>> This member function was added in C++17. Are there any intentions to
>> add it to __gnu_debug?
> There are probably other missing C++17 and C++20 changes too. It seems
> nobody else is using that type so if you care about it, I would
> encourage you to contribute to it.
>
Let me know if you started something regarding this Thomas. Otherwise 
I'll do it and also find a nice way to test __gnu_debug::string when 
running 'make check-debug'.


      reply	other threads:[~2022-06-30  4:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24  7:45 Frederick Virchanza Gotham
2022-06-24 10:07 ` Jonathan Wakely
2022-06-30  4:36   ` François Dumont [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=28ef4daf-20c0-0e14-f4f0-5a53397bff88@gmail.com \
    --to=frs.dumont@gmail.com \
    --cc=cauldwell.thomas@gmail.com \
    --cc=jwakely@redhat.com \
    --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).