From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3D0063858C54; Tue, 27 Feb 2024 05:12:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3D0063858C54 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1709010774; bh=sPYVVm6o7FaN5WHgewHiC74EeoR1UTNBj6/exZJpQEU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=pntvQrwnlINqiSLZSly9SdBUf8uU4wgpOdrMyI7Oxw3HHyVOUAQi+XDhSOXhfIfvA Ymq5QGG+YegGGoWgHs9DFuwNcsaIc9Gvoa+UI3RMsrWWQe+XHR7PbXXm77amiyeCGZ z9dTafqHkCbDLsjKXzyd1af00EM6HY+zmxDPvdf8= From: "barry.revzin at gmail dot com" 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: Tue, 27 Feb 2024 05:12:52 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: barry.revzin at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D104255 Barry Revzin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |barry.revzin at gmail dot = com --- Comment #8 from Barry Revzin --- (In reply to Patrick Palka from comment #2) > The error message is obscure, but it seems what GCC has issue with here is > the use of the function parameter seq2 in the trailing return type occurr= ing > outside of an unevaluated context. >=20 > I'm not totally sure if the testcase is valid > (https://eel.is/c++draft/basic.scope.param#note-1 might suggest it's not?= ), But we're not using the parameter for its "value" here (which I think means= in the sense of lvalue-to-rvalue conversion... as in reading a parameter of ty= pe int), so I don't think this would be a reason to reject?=