public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114479] [14 Regression] std::is_array_v<int[0]> changed from false to true in GCC 14 Date: Sun, 31 Mar 2024 10:05:42 +0000 [thread overview] Message-ID: <bug-114479-4-uH909pa4fd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114479-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114479 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- [dcl.array] says that for T[N] the value "N specifies the array bound, i.e., the number of elements in the array; N shall be greater than zero." So T[0] is not a valid array type. And std::is_array<T[0]> has never been true for any traditional implementation based on partial specialization of class templates, only when switching to an intrinsic __is_array that fails to accurately give the same behaviour as the std::is_array trait. Since the purpose of the __is_array intrinsic is to optimize the std::is_array trait, it should have the same behaviour. For the optimization to change the behaviour of the trait seems like the tail wagging the dog.
next prev parent reply other threads:[~2024-03-31 10:05 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-26 11:16 [Bug c++/114479] New: " nikolasklauser at berlin dot de 2024-03-26 11:42 ` [Bug c++/114479] [14 Regression] " pinskia at gcc dot gnu.org 2024-03-26 11:42 ` redi at gcc dot gnu.org 2024-03-27 7:57 ` rguenth at gcc dot gnu.org 2024-03-29 15:56 ` mpolacek at gcc dot gnu.org 2024-03-31 10:05 ` redi at gcc dot gnu.org [this message] 2024-04-01 14:28 ` mpolacek at gcc dot gnu.org 2024-04-01 15:25 ` arthur.j.odwyer at gmail dot com 2024-04-02 18:34 ` cvs-commit at gcc dot gnu.org 2024-04-02 18:35 ` mpolacek 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-114479-4-uH909pa4fd@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: linkBe 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).