public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95132] Concept checked after auto return type deduction
Date: Fri, 15 May 2020 13:57:40 +0000 [thread overview]
Message-ID: <bug-95132-4-NhtsR8AtTQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95132-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95132
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ppalka at gcc dot gnu.org
--- Comment #2 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to Francesco Biscani from comment #0)
> This is problematic because it means that another concept that would check
> whether or not bar() can be called with a specific argument type would fail
> with a hard compile time error, instead of marking the concept as not
> satisfied.
Would you have a concrete testcase for this behavior?
next prev parent reply other threads:[~2020-05-15 13:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 13:50 [Bug c++/95132] New: " bluescarni at gmail dot com
2020-05-14 15:26 ` [Bug c++/95132] " redi at gcc dot gnu.org
2020-05-15 13:57 ` ppalka at gcc dot gnu.org [this message]
2020-10-25 19:27 ` ppalka at gcc dot gnu.org
2020-10-28 15:47 ` cvs-commit at gcc dot gnu.org
2020-10-28 21:25 ` cvs-commit at gcc dot gnu.org
2020-10-28 21:34 ` ppalka 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-95132-4-NhtsR8AtTQ@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).