public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wjwray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/101960] New: std::tuple with an array element is rejected as a named return type
Date: Wed, 18 Aug 2021 14:01:46 +0000	[thread overview]
Message-ID: <bug-101960-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101960
           Summary: std::tuple with an array element is rejected as a
                    named return type
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: wjwray at gmail dot com
  Target Milestone: ---

This fails to compile, going back many revisions, in any std version:
https://godbolt.org/z/Kz9Mnz9aW

    #include <tuple>

    std::tuple<int[1]> f() {
        std::tuple<int[1]> t;
        return t;
    }

GCC rejects with:    ​error: array used as initializer
Clang rejects with:  error: array initializer must be an initializer list

(The Compiler Explorer link shows it working in Clang+libc++ and MSVC.)

However, this works:

    std::tuple<int[1]> g() { return {}; }

and so does this (workaround: return by-reference, then copy):

    constexpr std::tuple<int[1]>& h(std::tuple<int[1]>&& t = {}) {
        return t;
    }
    constexpr auto t = h();

(The only way I find with libstdc++ to make a constexpr tuple<T[N]>)

             reply	other threads:[~2021-08-18 14:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 14:01 wjwray at gmail dot com [this message]
2021-08-18 14:26 ` [Bug libstdc++/101960] " redi at gcc dot gnu.org
2021-08-18 14:28 ` redi at gcc dot gnu.org
2021-08-19 12:03 ` cvs-commit at gcc dot gnu.org
2021-08-19 14:09 ` redi at gcc dot gnu.org
2021-09-03 17:02 ` hewillk at gmail dot com
2021-10-12 10:59 ` cvs-commit at gcc dot gnu.org
2021-10-12 15:49 ` cvs-commit at gcc dot gnu.org
2021-10-12 16:24 ` cvs-commit at gcc dot gnu.org
2021-10-12 17:46 ` 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-101960-4@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).