public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sfranzen85 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97214] ICE in lookup_template_class_1, at cp/pt.c:9896 Date: Sun, 27 Sep 2020 19:47:15 +0000 [thread overview] Message-ID: <bug-97214-4-1hyFSqdyPz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97214-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97214 --- Comment #1 from Steven Franzen <sfranzen85 at hotmail dot com> --- Bug 97219 looks similar. Unqualified name lookup should consider the scope containing the lambda, which here is a member function and also includes the full scope of its class. Similar example at http://en.cppreference.com/w/cpp/language/lambda: For the purpose of name lookup, determining the type and value of the this pointer and for accessing non-static class members, the body of the closure type's function call operator is considered in the context of the lambda-expression. struct X { int x, y; int operator()(int); void f() { // the context of the following lambda is the member function X::f [=]()->int { return operator()(this->x + y); // X::operator()(this->x + (*this).y) // this has type X* }; } };
next prev parent reply other threads:[~2020-09-27 19:47 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-26 15:38 [Bug c++/97214] New: " sfranzen85 at hotmail dot com 2020-09-27 19:47 ` sfranzen85 at hotmail dot com [this message] 2020-10-26 17:16 ` [Bug c++/97214] [8/9/10/11 Regression] " mpolacek at gcc dot gnu.org 2020-10-26 17:17 ` mpolacek at gcc dot gnu.org 2021-03-12 0:20 ` mpolacek 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-97214-4-1hyFSqdyPz@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).