See also T13588.

This is relatively ripe for implementation now that inline comments support suggested edits.

I think lint could reasonably emit two warnings about this:

I believe that covers all cases of this.

However, the existence of the original code might point at a bug in the "Variable Reused as Iterator" lint check: I would expect it to have prevented the original code in the first place.

Changes in T13209 make this the only mode.

This doesn't seem actionable and is likely mooted by T13098.

This feature has been removed in experimental and wilds, and I don't currently expect to restore it.

(Future me, see also PHI343.)

The above workaround is not reliable since it skips the files entirely vs checking the remaining characters.

Oops, I filed it in the wrong place, my apologies!

Please file feature requests through the community forum (https://discourse.phabricator-community.org) or a support pact (https://admin.phacility.com/book/phacility/article/support_pacts/).

Doh!, I was looking at the jshint engine before, not the eslint engine. It looks like phab doesn't have built-in support for eslint yet. But this looks promising: maybe the autofixing eslint reports *is* on an error-by-error basis.

At Facebook we have a custom arcanist lint engine that wraps eslint with a custom (JS) runner that extracts more info about each fix: