Problem with concurrent linter fixes
Summary
A blog post examining a problem where concurrent linter fixes can produce broken code. It compares ESLint's batch-fix approach with elm-review's one-at-a-time fixes, illustrating how applying multiple automated changes without re-analysis can lead to incorrect references, and discusses potential solutions.