public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104255] parsing function signature fails when it uses a function parameter outside of an unevaluated context Date: Wed, 02 Feb 2022 15:13:01 +0000 [thread overview] Message-ID: <bug-104255-4-ZIzCEsHyyg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104255-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104255 --- Comment #5 from Patrick Palka <ppalka at gcc dot gnu.org> --- (In reply to qingzhe huang from comment #4) > (In reply to Patrick Palka from comment #2) > > > > > error: use of parameter outside function body before ‘)’ token > > > > due to 'e' being used outside of an unevaluated context within the signature > > of the function. > > Sorry for my being unable to grasp your meaning before. Now I can see your > point that the "e" of A<f(e)> is from declaration of parameter of function > "g". Now that we agree the value from parameter clause should not be used in > trailing return type, then it should also not be used in requires clause > etc. > (https://eel.is/c++draft/basic.scope.param#1.3) > But this works: > > template<typename T> > auto f(int n) requires (n>0); That's because the constraint-expression of a requires clause is an unevaluated operand (wg21.link/temp.pre#9.sentence-4). (Though I think this example is strictly speaking ill-formed no diagnostic required because the constraint can never be satisfied (wg21.link/temp.res.general#6.2).) The check in question is in finish_id_expression_1: /* Also disallow uses of function parameters outside the function body, except inside an unevaluated context (i.e. decltype). */ if (TREE_CODE (decl) == PARM_DECL && DECL_CONTEXT (decl) == NULL_TREE && !cp_unevaluated_operand) { *error_msg = G_("use of parameter outside function body"); return error_mark_node; } > > This is violating our assumption. So, I am not convinced that > (https://eel.is/c++draft/basic.scope.param#note-1) > "A function parameter cannot be used for its value within the > parameter-declaration-clause" is really meaningful. Or I misunderstand it??? We should probably relax the above check to permit uses of function parameters with empty types even outside of unevaluated contexts, since we don't really care about the value of an empty type.
next prev parent reply other threads:[~2022-02-02 15:13 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-26 22:51 [Bug c++/104255] New: parsing trailing return type fails with parameter pack expansion when two parameter packs at present nickhuang99 at hotmail dot com 2022-01-27 20:49 ` [Bug c++/104255] " nickhuang99 at hotmail dot com 2022-01-28 15:11 ` ppalka at gcc dot gnu.org 2022-01-28 18:48 ` [Bug c++/104255] parsing function signature fails when it uses a function parameter outside of an unevaluated context nickhuang99 at hotmail dot com 2022-01-28 22:40 ` nickhuang99 at hotmail dot com 2022-02-02 15:13 ` ppalka at gcc dot gnu.org [this message] 2023-10-06 13:42 ` ppalka at gcc dot gnu.org 2023-11-08 21:54 ` ppalka at gcc dot gnu.org 2023-11-08 21:55 ` ppalka at gcc dot gnu.org 2024-02-27 5:12 ` barry.revzin at gmail 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-104255-4-ZIzCEsHyyg@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).