public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "robert.durkacz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106241] compiler can't handle large array of strings
Date: Sun, 10 Jul 2022 09:59:06 +0000 [thread overview]
Message-ID: <bug-106241-4-aeBWxKzZGx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106241-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106241
--- Comment #5 from Robert Durkacz <robert.durkacz at gmail dot com> ---
That is a good idea.
On Sun, 10 Jul 2022 at 19:56, redi at gcc dot gnu.org <
gcc-bugzilla@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106241
>
> --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
> Yes, like https://wg21.link/p1967r7
>
> But in the meantime, you can create a static array of trivial types (not
> std::string) and then iterate over it at runtime to copy the values into
> the
> data structure you want to use (a multimap containing strings, or
> whatever).
>
> --
> You are receiving this mail because:
> You reported the bug.
next prev parent reply other threads:[~2022-07-10 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 11:33 [Bug c++/106241] New: " robert.durkacz at gmail dot com
2022-07-09 11:55 ` [Bug c++/106241] " schwab@linux-m68k.org
2022-07-09 16:20 ` redi at gcc dot gnu.org
2022-07-10 1:32 ` robert.durkacz at gmail dot com
2022-07-10 9:56 ` redi at gcc dot gnu.org
2022-07-10 9:59 ` robert.durkacz at gmail dot com [this message]
2022-07-10 20:39 ` pinskia at gcc dot gnu.org
2022-07-11 11:00 ` redi at gcc dot gnu.org
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=bug-106241-4-aeBWxKzZGx@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).