From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 02CD5385840B; Tue, 9 Apr 2024 00:11:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 02CD5385840B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712621485; bh=RPcIQtUlcqPYJGVyeekZDtZiO/4LElMoFi1F9sor0jQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=QAI0qgA0wETrwjfZYdNZvsF77bI7HLu5+OrpBQ9no7TacQYXUUkl77k1pwBjOPZiY /JJzDImGPr3Hx3EtX6Om8vJLbp57vY0x12sWwiDDPhVn3C+jH6eGeqp5x8ncXYss8I Zq7qZSyw15ZrUG2VaKoVVRw9Wr6CVouky/iHPGZ0= From: "pinskia at gcc dot gnu.org" To: gcc-rust@gcc.gnu.org Subject: [Bug rust/114629] rust-ast-resolve-expr contains bloated code for funny_error Date: Tue, 09 Apr 2024 00:11:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rust X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia 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: 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=3D114629 --- Comment #5 from Andrew Pinski --- (In reply to Pierre-Emmanuel Patry from comment #2) > I can see the problem with the message, but I don't think we can remove t= he > behavior as we have to match rustc's behavior. The compiler has to ICE wh= en > meeting this identifier. I suggest changing the message to rustc's one "It > looks like you're trying to break rust; would you like some ICE?" and > removing the "gcc" identifier check. Really this sounds like a bad idea to copy 100% of what rustc does. Instead= we should follow the rust language specification (hopefully that actually exis= ts). While you are at it, it would be useful to add a link to the rust langauge specification (like there is for almost all other languages [I see objectiv= e-C is not listed]) to https://gcc.gnu.org/readings.html . --=20 You are receiving this mail because: You are on the CC list for the bug.=