public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hans.dembinski at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/97663] New: [c++17] Function with return type 'unsigned' in nested namespace misinterpreted as deduction guide
Date: Sun, 01 Nov 2020 15:07:43 +0000	[thread overview]
Message-ID: <bug-97663-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 97663
           Summary: [c++17] Function with return type 'unsigned' in nested
                    namespace misinterpreted as deduction guide
           Product: gcc
           Version: 10.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hans.dembinski at gmail dot com
  Target Milestone: ---

g++ with -std=c++17 since version 7.1 up to current trunk misdetects 'bar::foo'
the following code as a deduction guide for 'struct foo':

```
template <class T> struct foo {};

namespace bar {

unsigned foo();

}
```

Code on Godbolt: https://godbolt.org/z/6E4efY

Workarounds:
- Use 'unsigned int foo()'
- Use 'auto foo() -> unsigned'.

Related issue with more context:
https://github.com/boostorg/histogram/issues/290

             reply	other threads:[~2020-11-01 15:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-01 15:07 hans.dembinski at gmail dot com [this message]
2020-11-01 16:54 ` [Bug c++/97663] " ville.voutilainen at gmail dot com
2020-11-02 11:00 ` jakub at gcc dot gnu.org
2020-11-02 11:40 ` jakub at gcc dot gnu.org
2020-11-03 20:43 ` cvs-commit at gcc dot gnu.org
2020-11-12 10:05 ` cvs-commit at gcc dot gnu.org
2021-04-20 23:30 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:48 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:07 ` jakub at gcc dot gnu.org
2021-09-11 14:29 ` pinskia 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-97663-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).