public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eiband at mail dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107773] New: Class members do not hide nested types Date: Sun, 20 Nov 2022 19:28:31 +0000 [thread overview] Message-ID: <bug-107773-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107773 Bug ID: 107773 Summary: Class members do not hide nested types Product: gcc Version: 11.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: eiband at mail dot de Target Milestone: --- The following program exits with code 1. test.cpp: struct a { using get = void; }; struct b : a { int get(int i) const; }; template <typename T> concept c = requires { typename T::get; }; int main() { return c<b>; } $ g++ test.cpp -std=c++20 $ ./a.out $ echo $? 1 Expected is exit code 0, because T::get is not a type for T=b. The code snippet is based on user "apple apple"'s comment on https://stackoverflow.com/questions/74509418/why-does-member-function-not-hide-type-alias-in-base-class-when-compiling-with-g. User "n. m." also notes that GCC happily compiles https://eel.is/c++draft/temp.res.general#example-4 which does not use concepts and should emit an error. $ g++ -v gcc version 11.1.0 (Ubuntu 11.1.0-1ubuntu1~20.04)
next reply other threads:[~2022-11-20 19:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-20 19:28 eiband at mail dot de [this message] 2022-11-20 19:47 ` [Bug c++/107773] " pinskia at gcc dot gnu.org 2022-11-28 16:41 ` [Bug c++/107773] Class members do not hide inherited types inside requires ppalka at gcc dot gnu.org 2022-11-28 21:00 ` ppalka at gcc dot gnu.org 2023-02-16 16:12 ` cvs-commit at gcc dot gnu.org 2023-02-16 16:27 ` 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-107773-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).