[Bug c++/82980] [9/10/11/12 Regression] template keyword should not be required for captured decl of the "base" type since r6-6866-gff2faafcf689b6c2

["cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82980

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:

https://gcc.gnu.org/g:74b2e20222cf4fb24b90561ddb6f0989738bb722

commit r12-8165-g74b2e20222cf4fb24b90561ddb6f0989738bb722
Author: Jason Merrill <jason@redhat.com>
Date:   Thu Apr 14 08:16:45 2022 -0400

    c++: lambda and the current instantiation [PR82980]

    When a captured variable is type-dependent, we've expressed the type of the
    capture field and proxy with a decltype variant.  But if the type is "the
    current instantiation", we need to be able to see that so that we can do
    lookup inside it just like we could with the captured variable itself.

    I also tried looking through lambda capture in
    cp_parser_postfix_dot_deref_expression, but this way seems cleaner.  I plan
    to treat more types as deducible in stage 1.

    I considered also using this in do_auto_deduction, but think that would be
    wrong: [temp.dep.expr] says an id-expression is type-dependent if it is
    "associated by name lookup with a variable declared with a type that
    contains a placeholder type where the initializer is type-dependent".  That
    doesn't clearly exclude deducing a dependent type from the initializer, but
    it seems like a barrier, and other implementations agree.

            PR c++/82980

    gcc/cp/ChangeLog:

            * lambda.cc (type_deducible_expression_p): New.
            (lambda_capture_field_type): Check it.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/lambda/lambda-current-inst1.C: New test.