public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cassio.neri at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56693] New: Fail to ignore const qualification on top of a function type.
Date: Fri, 22 Mar 2013 23:30:00 -0000	[thread overview]
Message-ID: <bug-56693-4@http.gcc.gnu.org/bugzilla/> (raw)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56693

             Bug #: 56693
           Summary: Fail to ignore const qualification on top of a
                    function type.
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: cassio.neri@gmail.com


The following code:

void f() {}

template <typename T> void g(const T*) { }

int main() {
    g(f);
}

raises an error with this note:

    types 'const T' and 'void()' have incompatible cv-qualifiers

Attempting to instantiate g creates a function that takes a pointer to a const
T where T = void(). Since there's no such thing as a "const function", this
explains the note. However, C++11 8.3.5/6 says

"The effect of a cv-qualifier-seq in a function declarator is not the same as
adding cv-qualification on top of the function type. In the latter case, the
cv-qualifiers are ignored."

Hence, the const qualifier should be ignored and the code should compile. (It
does compile with clang and visual studio.)

For more information see:
http://stackoverflow.com/questions/15578298/can-a-const-t-match-a-pointer-to-free-function


             reply	other threads:[~2013-03-22 23:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 23:30 cassio.neri at gmail dot com [this message]
2013-03-23 12:20 ` [Bug c++/56693] " daniel.kruegler at googlemail dot com
2013-03-23 15:03 ` [Bug c++/56693] [DR 1584] " redi at gcc dot gnu.org
2021-08-12  4:06 ` 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-56693-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).