public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95153] Arrays of 'const void *' should not be copyable in C++20
Date: Fri, 11 Mar 2022 18:29:53 +0000	[thread overview]
Message-ID: <bug-95153-4-GZg1Z8OYUF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95153-4@http.gcc.gnu.org/bugzilla/>

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

Barry Revzin <barry.revzin at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |barry.revzin at gmail dot com

--- Comment #5 from Barry Revzin <barry.revzin at gmail dot com> ---
Just to follow up, gcc trunk right now does this:

int main() {
    int a[3]{};
    void const* b[3](a);  // ok

    void const* c[3]{};
    void const* d[3](c);  // error: array must be initialized with a
brace-enclosed initializer
}

If 'd' is actually an error, then it's not because of that, so at the very
least, the diagnostic is wrong.

      parent reply	other threads:[~2022-03-11 18:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 13:37 [Bug c++/95153] New: Arrays of 'const void *' should not be copyable alisdairm at me dot com
2020-05-15 14:02 ` [Bug c++/95153] " alisdairm at me dot com
2020-05-15 16:39 ` [Bug c++/95153] Arrays of 'const void *' should not be copyable in C++20 rs2740 at gmail dot com
2020-07-06 12:28 ` alisdairm at me dot com
2020-07-06 12:52 ` redi at gcc dot gnu.org
2022-03-11 18:29 ` barry.revzin at gmail dot com [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=bug-95153-4-GZg1Z8OYUF@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).