public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ojman101 at protonmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95066] New: [C++ 20] Incorrect valid compilation with a conditional explicit Date: Mon, 11 May 2020 17:50:04 +0000 [thread overview] Message-ID: <bug-95066-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95066 Bug ID: 95066 Summary: [C++ 20] Incorrect valid compilation with a conditional explicit Product: gcc Version: 9.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ojman101 at protonmail dot com Target Milestone: --- The code below is invalid C++, the line "Foo<int> b = a;" should fail to compile as implicitly casting is made illegal by the conditional explicit using the "IsSafelyCastable" predicate. ---------------------------------------------------------------- #include <type_traits> template <typename, typename> class IsSafelyCastable : public std::false_type {}; template <> class IsSafelyCastable<int, float> : public std::true_type {}; template <typename T> struct Foo { template <typename U> explicit(!IsSafelyCastable<T, U>::value) operator Foo<U>(); }; template <typename T> template <typename U> Foo<T>::operator Foo<U>() { return {}; } int main() { Foo<float> a; Foo<int> b = a; } ---------------------------------------------------------------- Clang 10 correctly evaluates the explicit condition to be true and blocks the implicit cast. However, GCC 9.3.0 successfully compiles without any errors. I believe this to be a GCC bug as subtle changes can make GCC produce the correct error. For example, moving the definition of the function to be inline with the declaration.
next reply other threads:[~2020-05-11 17:50 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-11 17:50 ojman101 at protonmail dot com [this message] 2020-05-11 17:57 ` [Bug c++/95066] " ojman101 at protonmail dot com 2020-05-11 18:26 ` [Bug c++/95066] [C++ 20] Incorrect successful " mpolacek at gcc dot gnu.org 2020-05-11 22:00 ` mpolacek at gcc dot gnu.org 2020-05-11 23:07 ` mpolacek at gcc dot gnu.org 2020-05-13 20:26 ` cvs-commit at gcc dot gnu.org 2020-06-11 20:33 ` cvs-commit at gcc dot gnu.org 2020-06-11 20:33 ` mpolacek 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-95066-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: linkBe 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).