public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jacek.olczyk98 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103760] Invalid expression inside lambda inside compound requirement causes an error instead of concept satisfaction failure
Date: Sun, 19 Dec 2021 09:30:46 +0000 [thread overview]
Message-ID: <bug-103760-4-jYirmQwxtB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103760-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103760
--- Comment #4 from Jacek Olczyk <jacek.olczyk98 at gmail dot com> ---
(In reply to Patrick Palka from comment #2)
> GCC's behavior appears to be correct here (though perhaps less useful than
> Clang's). According to wg21.link/temp.deduct.general#9 a lambda expression
> isn't part of the immediate context, so substitution failure from within the
> lambda ought to be a hard error, not a SFINAE error. Note that Clang also
> doesn't reject the first four examples from that paragraph.
Forgive me if I'm wrong (it's my first time reading into the standard), but
this seems to be from a section explicitly talking about function templates,
not templates in general - and function templates seem to be somewhat of a
special case in many ways. I have not, however, been able to find the portion
of the standard which delves into the relevant behavior in other templates.
next prev parent reply other threads:[~2021-12-19 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 20:57 [Bug c++/103760] New: " jacek.olczyk98 at gmail dot com
2021-12-17 21:13 ` [Bug c++/103760] " pinskia at gcc dot gnu.org
2021-12-18 15:44 ` ppalka at gcc dot gnu.org
2021-12-18 22:40 ` pinskia at gcc dot gnu.org
2021-12-19 9:30 ` jacek.olczyk98 at gmail dot com [this message]
2021-12-20 14:09 ` ppalka at gcc dot gnu.org
2023-01-03 18:27 ` ppalka at gcc dot gnu.org
2023-06-13 1:49 ` danakj at orodu dot net
2023-06-13 2:12 ` 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-103760-4-jYirmQwxtB@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).