From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3877E388E814; Tue, 9 Jun 2020 23:04:16 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3877E388E814 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1591743856; bh=Hkq3GGOLfU+KKYYkFTbnkObYcQpOydslpMRoavaHBIQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=UGkQjlQi5czvOjY+BP/3OUuGoLOBFqq9AtVAufiHGnVghRGXiaZYjQYcYEsY50gS1 KJkZGuaAhwD63VUONEzL+J0FoAImUDeLgdPuTL8rBzyTEOGA/EP575DHVp/xvfiF53 QauUjImZEy/lySB8DDuDo4aXJYCakNibUCnPlDMs= From: "mpolacek at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95564] GCC rejects lambda expression with "noexcept(1+1)" Date: Tue, 09 Jun 2020 23:04:15 +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: 11.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: mpolacek at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jun 2020 23:04:16 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95564 Marek Polacek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpolacek at gcc dot gnu.org --- Comment #1 from Marek Polacek --- There was some discussion on the Core C++ mailing list about whether a conversion to bool should be narrowing, and though opinions differed, I thi= nk gcc isn't incorrect in rejecting this code.=