public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guille at cal dot berkeley.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67910] New: Two autos in a single function confuses the type system
Date: Fri, 09 Oct 2015 16:46:00 -0000	[thread overview]
Message-ID: <bug-67910-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 67910
           Summary: Two autos in a single function confuses the type
                    system
           Product: gcc
           Version: 5.2.0
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: guille at cal dot berkeley.edu
  Target Milestone: ---

The following code does not compile on 5.2.0:



struct A {};
struct B {};

static auto f(auto b) -> A { return A(); }

int main()
{
    A a = f(B());
    return 0;
}

whereas the following *does* compile:


struct A {};
struct B {};

static auto f(B b) -> A { return A(); }


int main()
{
    __attribute__((unused)) A a = f(B());
    return 0;
}


In the first (failing) case, the type system thinks that 'f' returns the same
type as the first auto *argument*, even though the return type is specified to
be 'A'.


             reply	other threads:[~2015-10-09 16:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 16:46 guille at cal dot berkeley.edu [this message]
2015-10-09 16:48 ` [Bug c++/67910] " guille at cal dot berkeley.edu
2015-10-09 16:50 ` guille at cal dot berkeley.edu
2015-10-09 16:51 ` guille at cal dot berkeley.edu
2015-10-09 17:17 ` glisse at gcc dot gnu.org
2015-10-09 19:44 ` guille at cal dot berkeley.edu
2015-10-10  5:39 ` guille at cal dot berkeley.edu
2015-10-10  5:41 ` guille at cal dot berkeley.edu

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-67910-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).