public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102609] [C++23] P0847R7 - Deducing this Date: Tue, 09 Jan 2024 21:56:55 +0000 [thread overview] Message-ID: <bug-102609-4-m2pRw9ALvo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102609-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102609 --- Comment #23 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:07d09f0af100a9873982fba663800d87bfd73585 commit r14-7077-g07d09f0af100a9873982fba663800d87bfd73585 Author: waffl3x <waffl3x@protonmail.com> Date: Sun Jan 7 00:53:32 2024 +0000 c++: P0847R7 (deducing this) - xobj lambdas. [PR102609] This implements support for xobj lambdas. There are extensive tests included, but not exhaustive. Dependent lambdas should work and have been tested lightly, but we need more exhaustive tests for them. PR c++/102609 gcc/cp/ChangeLog: PR c++/102609 C++23 P0847R7 (deducing this) - xobj lambdas. * lambda.cc (build_capture_proxy): Don't fold direct object types. * parser.cc (cp_parser_lambda_declarator_opt): Handle xobj lambdas, diagnostics. Comments also updated. * pt.cc (tsubst_function_decl): Handle xobj lambdas. Check object type of xobj lambda call operator, diagnose incorrect types. (tsubst_lambda_expr): Update comment. * semantics.cc (finish_decltype_type): Also consider by-value object parameter qualifications. gcc/testsuite/ChangeLog: PR c++/102609 C++23 P0847R7 (deducing this) - xobj lambdas. * g++.dg/cpp23/explicit-obj-diagnostics8.C: New test. * g++.dg/cpp23/explicit-obj-lambda1.C: New test. * g++.dg/cpp23/explicit-obj-lambda10.C: New test. * g++.dg/cpp23/explicit-obj-lambda11.C: New test. * g++.dg/cpp23/explicit-obj-lambda12.C: New test. * g++.dg/cpp23/explicit-obj-lambda13.C: New test. * g++.dg/cpp23/explicit-obj-lambda2.C: New test. * g++.dg/cpp23/explicit-obj-lambda3.C: New test. * g++.dg/cpp23/explicit-obj-lambda4.C: New test. * g++.dg/cpp23/explicit-obj-lambda5.C: New test. * g++.dg/cpp23/explicit-obj-lambda6.C: New test. * g++.dg/cpp23/explicit-obj-lambda7.C: New test. * g++.dg/cpp23/explicit-obj-lambda8.C: New test. * g++.dg/cpp23/explicit-obj-lambda9.C: New test. Signed-off-by: Waffl3x <waffl3x@protonmail.com>
next prev parent reply other threads:[~2024-01-09 21:56 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-05 15:56 [Bug c++/102609] New: " mpolacek at gcc dot gnu.org 2021-11-28 11:33 ` [Bug c++/102609] " pinskia at gcc dot gnu.org 2023-06-12 23:37 ` mpolacek at gcc dot gnu.org 2023-08-16 18:29 ` waffl3x at protonmail dot com 2023-08-16 18:48 ` gasper.azman at gmail dot com 2023-08-16 18:50 ` gasper.azman at gmail dot com 2023-08-16 21:58 ` waffl3x at protonmail dot com 2023-08-19 8:44 ` waffl3x at protonmail dot com 2023-08-19 9:38 ` redi at gcc dot gnu.org 2023-08-19 9:43 ` redi at gcc dot gnu.org 2023-08-19 16:10 ` gasper.azman at gmail dot com 2023-08-19 21:24 ` waffl3x at protonmail dot com 2023-08-20 14:21 ` gasper.azman at gmail dot com 2023-08-21 1:24 ` waffl3x at protonmail dot com 2023-08-21 15:17 ` barry.revzin at gmail dot com 2023-08-25 11:28 ` waffl3x at protonmail dot com 2023-08-31 6:50 ` waffl3x at protonmail dot com 2023-08-31 9:28 ` gasper.azman at gmail dot com 2023-09-02 8:54 ` waffl3x at protonmail dot com 2023-09-02 22:30 ` gasper.azman at gmail dot com 2024-01-09 21:56 ` cvs-commit at gcc dot gnu.org 2024-01-09 21:56 ` cvs-commit at gcc dot gnu.org 2024-01-09 21:56 ` cvs-commit at gcc dot gnu.org 2024-01-09 21:56 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-09 21:57 ` cvs-commit at gcc dot gnu.org 2024-01-11 20:47 ` corentinjabot at gmail dot com 2024-01-11 21:08 ` waffl3x at protonmail dot com 2024-01-11 22:00 ` gasper.azman at gmail dot com 2024-01-11 22:01 ` jakub at gcc dot gnu.org 2024-01-12 0:26 ` waffl3x at protonmail 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-102609-4-m2pRw9ALvo@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).