public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109680] [13/14 Regression] is_convertible<int() const, int(*)()> incorrectly true
Date: Wed, 10 May 2023 22:25:02 +0000	[thread overview]
Message-ID: <bug-109680-4-6tFsHlrtDy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109680-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:

https://gcc.gnu.org/g:4c2ffb02fd4104d77c5d907662f04434dc4c3fe8

commit r14-669-g4c2ffb02fd4104d77c5d907662f04434dc4c3fe8
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue May 2 17:36:00 2023 -0400

    c++: wrong std::is_convertible with cv-qual fn [PR109680]

    This PR points out that std::is_convertible has given the wrong answer
    in

      static_assert (!std::is_convertible_v <int () const, int (*) ()>, "");

    since r13-2822 implemented __is_{,nothrow_}convertible.

    std::is_convertible uses the imaginary

      To test() { return std::declval<From>(); }

    to do its job.  Here, From is 'int () const'.  std::declval is defined as:

      template<class T>
      typename std::add_rvalue_reference<T>::type declval() noexcept;

    std::add_rvalue_reference is defined as "If T is a function type that
    has no cv- or ref- qualifier or an object type, provides a member typedef
    type which is T&&, otherwise type is T."

    In our case, T is cv-qualified, so the result is T, so we end up with

      int () const declval() noexcept;

    which is invalid.  In other words, this is pretty much like:

      using T = int () const;
      T fn1(); // bad, fn returning a fn
      T& fn2(); // bad, cannot declare reference to qualified function type
      T* fn3(); // bad, cannot declare pointer to qualified function type

      using U = int ();
      U fn4(); // bad, fn returning a fn
      U& fn5(); // OK
      U* fn6(); // OK

    I think is_convertible_helper needs to simulate std::declval better.
    To that end, I'm introducing build_trait_object, to be used where
    a declval is needed.

            PR c++/109680

    gcc/cp/ChangeLog:

            * method.cc (build_trait_object): New.
            (assignable_expr): Use it.
            (ref_xes_from_temporary): Likewise.
            (is_convertible_helper): Likewise.  Check FUNC_OR_METHOD_TYPE_P.

    gcc/testsuite/ChangeLog:

            * g++.dg/ext/is_convertible6.C: New test.

  parent reply	other threads:[~2023-05-10 22:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-29 17:13 [Bug c++/109680] New: Regression where `int() const` is considered convertible to `int(*)()` dpsicilia at gmail dot com
2023-04-29 17:28 ` [Bug c++/109680] " pinskia at gcc dot gnu.org
2023-04-29 17:42 ` [Bug c++/109680] [13/14 Regression] is_convertible<int() const, int(*)()> incorrectly true pinskia at gcc dot gnu.org
2023-05-01  9:03 ` jakub at gcc dot gnu.org
2023-05-01 16:09 ` mpolacek at gcc dot gnu.org
2023-05-01 16:32 ` jakub at gcc dot gnu.org
2023-05-01 23:13 ` mpolacek at gcc dot gnu.org
2023-05-02  7:36 ` jakub at gcc dot gnu.org
2023-05-02 19:22 ` mpolacek at gcc dot gnu.org
2023-05-03 12:58 ` mpolacek at gcc dot gnu.org
2023-05-10 22:25 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-10 22:25 ` [Bug c++/109680] [13 " mpolacek at gcc dot gnu.org
2023-07-03 12:08 ` dpsicilia at gmail dot com
2023-07-03 12:36 ` redi at gcc dot gnu.org
2023-07-27  9:25 ` rguenth at gcc dot gnu.org
2023-08-04 18:08 ` pinskia at gcc dot gnu.org
2024-05-21  9:14 ` jakub 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-109680-4-6tFsHlrtDy@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).