Path: csiph.com!xmission!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end
From: Kaz Kylheku <937-053-0959@kylheku.com>
Newsgroups: comp.compilers
Subject: Re: Spell checking identifiers
Date: Wed, 24 Jun 2020 18:12:35 +0000 (UTC)
Organization: Aioe.org NNTP Server
Lines: 19
Sender: news@iecc.com
Approved: comp.compilers@iecc.com
Message-ID: <20-06-014@comp.compilers>
References: <20-06-010@comp.compilers>
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="40754"; mail-complaints-to="abuse@iecc.com"
Keywords: lex, errors
Posted-Date: 24 Jun 2020 14:45:52 EDT
X-submission-address: compilers@iecc.com
X-moderator-address: compilers-request@iecc.com
X-FAQ-and-archives: http://compilers.iecc.com
Xref: csiph.com comp.compilers:2535

On 2020-06-23, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
> Dear c.compilers,
>
> While experimenting with Rust, I came across this suggestion.
>
>   --> foo.rs:5:9
>    |
> 5 |     return j; // the variable, not the type.
>    |            ^ help: a local variable with a similar name exists: `i`
>
> Here it is suggesting i where I typed j.  This is the same problem as
> spell checking identifiers with fuzzy matching, so apologies for a po-
> tentially misleading subject.

I don't find these kinds of childish diagnostic messages useful at all.

They have started to appear in GCC also.

The good old "undeclared identifier `j`" requires no update, thanks.