From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 01F763858CDA; Thu,  1 Dec 2022 08:41:18 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 01F763858CDA
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1669884079;
	bh=MzQI5c5zV4LKnl72HYuaGvjfp5V+lN61RqSaIMeU0F8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=gm6OTGR6Pdno5vWq+kXQujPOfB8lGWnv7mueX+VE11xQuVeVcE2Ns8STRt62rOLzk
	 f81en8mAUNhCErOaft7smByJeaFGtuHsOQ9rb2RcoAA60KXiFJgTfpuEM4RrW300/5
	 2qIiY4mFCvfrBayIlcZN3Vmxq5ttaWogbhopZ/MM=
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/772] Statement expressions issues
Date: Thu, 01 Dec 2022 08:41:11 +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: 2.97
X-Bugzilla-Keywords: accepts-invalid, stmt-expr
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
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: 
Message-ID: <bug-772-4-m2EsNnC9rc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-772-4@http.gcc.gnu.org/bugzilla/>
References: <bug-772-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

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

--- Comment #24 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #22)
> oops wait I thought this was a meta-bug for a moment... although, maybe i=
t's
> time to start using it as one?

Never mind about this; looks like there's a keyword (stmt-expr) now to use
instead...=