public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sebi707 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/67240] New: [concepts] Implicit conversion constraints are not respected Date: Sun, 16 Aug 2015 18:09:00 -0000 [thread overview] Message-ID: <bug-67240-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67240 Bug ID: 67240 Summary: [concepts] Implicit conversion constraints are not respected Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: sebi707 at gmail dot com Target Milestone: --- Using the trailing return type to add constraints does not work in some cases. The following code should not compile: int foo(int x) { return x; } template <typename T> concept bool C1 = requires (T x) { {foo(x)} -> int&; }; template <typename T> concept bool C2 = requires (T x) { {foo(x)} -> void; }; static_assert( C1<int> ); static_assert( C2<int> ); However this compiles just fine with r226884.
next reply other threads:[~2015-08-16 18:09 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-16 18:09 sebi707 at gmail dot com [this message] 2015-08-17 9:20 ` [Bug c++/67240] " redi at gcc dot gnu.org 2015-08-21 18:33 ` jason at gcc dot gnu.org 2015-08-21 18:33 ` jason 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-67240-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).