public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fchelnokov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/115280] New: Concept can access private alias in a classs
Date: Wed, 29 May 2024 16:31:05 +0000 [thread overview]
Message-ID: <bug-115280-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115280
Bug ID: 115280
Summary: Concept can access private alias in a classs
Product: gcc
Version: 14.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: fchelnokov at gmail dot com
Target Milestone: ---
This program
```
#include <concepts>
class A {
using X = int;
};
template<typename T>
concept C = requires(T t) {
{ t } -> std::convertible_to<A::X>;
};
static_assert(C<int>);
```
is invalid and rejected by Clang with the error:
> error: 'X' is a private member of 'A'
But GCC accepts the program just fine, which looks wrong, online demo:
https://gcc.godbolt.org/z/nra6fExxG
next reply other threads:[~2024-05-29 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 16:31 fchelnokov at gmail dot com [this message]
2024-05-29 16:37 ` [Bug c++/115280] Concept can access private alias/typedef in a non-dependent classs 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-115280-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: 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).