public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus.kuehni at triviso dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98933] P0784R7 example support: constexpr new
Date: Tue, 02 Feb 2021 14:32:41 +0000	[thread overview]
Message-ID: <bug-98933-4-VH3o4i8Wmk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98933-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98933

--- Comment #2 from Mark <markus.kuehni at triviso dot ch> ---
(In reply to Jakub Jelinek from comment #1)
> Have you noticed the
> In Kona 2019, this approach was considered too brittle, and as a result
> non-transient allocation was removed from the feature set. 
> line just below that example?
> This is not valid C++20.

So just to understand this right. It is ok as long as it does not survive
compilation?

But how are you going to implement constexpr std::vector and std::string then? 

(I'm actually somehow trying to bridge the time until that happens ;-)

  parent reply	other threads:[~2021-02-02 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02 14:16 [Bug c++/98933] New: " markus.kuehni at triviso dot ch
2021-02-02 14:23 ` [Bug c++/98933] " jakub at gcc dot gnu.org
2021-02-02 14:32 ` markus.kuehni at triviso dot ch [this message]
2021-02-02 14:37 ` jakub at gcc dot gnu.org
2021-02-02 14:43 ` markus.kuehni at triviso dot ch
2021-02-03 16:17 ` markus.kuehni at triviso dot ch

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-98933-4-VH3o4i8Wmk@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).