public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steve+gcc at tecwec dot eu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104111] [DR2589] Concept evaluation depends on context where it was first checked
Date: Thu, 22 Feb 2024 17:11:51 +0000 [thread overview]
Message-ID: <bug-104111-4-0jKHCLRPkY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104111-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104111
Eric Estievenart <steve+gcc at tecwec dot eu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |steve+gcc at tecwec dot eu
--- Comment #9 from Eric Estievenart <steve+gcc at tecwec dot eu> ---
By the way, the following code exhibits another related weirdness, without
access control being involved:
```
#include <concepts>
struct Op
{
void operator()( auto x ) const = delete; // want only explicit
customization in scope
};
struct S {};
static_assert( !std::invocable<Op, S> );
template<> void Op::operator()( S ) const {} // now Op is invocable on S
static_assert( std::invocable<Op, S> ); // so should not fail ! but...
```
(https://godbolt.org/z/Wa6rxeMvP)
Commenting the first assert makes the second suddenly pass...
Quantum physicist would say "spooky action at a distance" ;-)
Hope this helps,
Best.
next prev parent reply other threads:[~2024-02-22 17:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 8:21 [Bug c++/104111] New: " fchelnokov at gmail dot com
2022-01-19 8:22 ` [Bug c++/104111] " fchelnokov at gmail dot com
2022-01-19 8:42 ` pinskia at gcc dot gnu.org
2022-01-19 14:19 ` ppalka at gcc dot gnu.org
2022-01-21 14:27 ` ppalka at gcc dot gnu.org
2022-04-21 7:51 ` rguenth at gcc dot gnu.org
2022-05-27 17:58 ` jason at gcc dot gnu.org
2022-05-27 22:02 ` jason at gcc dot gnu.org
2022-05-31 19:29 ` [Bug c++/104111] [DR2589] " jason at gcc dot gnu.org
2023-05-29 10:06 ` jakub at gcc dot gnu.org
2024-02-22 17:11 ` steve+gcc at tecwec dot eu [this message]
2024-02-22 22:50 ` webrown.cpp at gmail dot com
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-104111-4-0jKHCLRPkY@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).