From: Ville Voutilainen <ville.voutilainen@gmail.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: transparent proxy of string_view as key for associative containers.
Date: Sat, 28 Nov 2020 13:17:48 +0200 [thread overview]
Message-ID: <CAFk2RUY52BZE0mNC+zgayWYDyMxKB_Sd0k1x5zpROPGYzEfHuw@mail.gmail.com> (raw)
In-Reply-To: <a0796aba-d027-49a5-521d-3bd1ddf8673f@gmail.com>
On Sat, 28 Nov 2020 at 13:02, François Dumont via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> Hi
>
> Just for information I am starting the work on this following this
> paper: http://wg21.link/p1690r1
Thanks for the heads-up, because I was about to start doing that. All
yours, go ahead, I'll hack on something else.
I took a brief look at this, and we basically need to add the
templated overloads all the way down to the hash table,
but other than that, there doesn't seem to be anything too tedious in this.
next prev parent reply other threads:[~2020-11-28 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 6:43 sotrdg sotrdg
2020-11-16 7:26 ` Daniel Krügler
2020-11-16 9:57 ` Jonathan Wakely
2020-11-28 11:02 ` François Dumont
2020-11-28 11:17 ` Ville Voutilainen [this message]
2020-11-28 13:30 ` François Dumont
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=CAFk2RUY52BZE0mNC+zgayWYDyMxKB_Sd0k1x5zpROPGYzEfHuw@mail.gmail.com \
--to=ville.voutilainen@gmail.com \
--cc=frs.dumont@gmail.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).