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 A1F16385840D; Tue,  9 Apr 2024 10:57:20 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A1F16385840D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1712660240;
	bh=m811kNGXtE54N8UkvNk1wemhro6LsTl6KYa+Qb3lq8M=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=nvSRIBXvhHwm1PWgykbjv3keEO973Mat7J1hN6hNljZRiXLHn465IX6/7KEa3vSHn
	 lPnorpgtdJksr+Vj/Fhx5mX7zeqX9HDKIgB/7/sJDbP0T2vTvomhk4Rtqoaex4xLCj
	 HKGfbTNcDaIhV4e2Loe4Ej8UeavxAa1AjWNP5AyE=
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rust/114629] rust-ast-resolve-expr contains bloated code for
 funny_error
Date: Tue, 09 Apr 2024 10:57:17 +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: iains 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-114629-4-IBNZekBO7S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114629-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114629-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=3D114629

--- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #5)
> (In reply to Pierre-Emmanuel Patry from comment #2)


> 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
> objective-C is not listed]) to https://gcc.gnu.org/readings.html .

This is getting a bit off-topic for the current PR - but, for the record, I=
 am
not aware of any formal spec for Objective-C/C++ - the API is described in
Apple's developer documentation and compliance is assessed (at least by me)=
 in
terms of "do we implement the things that we claim, in the same way as the
system compiler"?=