Consider supporting autofix.

[ryaneberly]

---- from @denuno
That would be a pretty interesting thing to have in CFLint itself, actually, along with a mode where you could enable auto-fixing (or maybe auto-ignoring)... e.g. instead of just warning about an unscoped var, optionally have it var scope it... yeah, something like enabling "suggestions", where it says what rule is broke and then also (if it is easy to figure out) shows a proposed fix.

Something to think about at least. For sure would want it to be optional, as something like that would slow things down a bit I reckon.

[KamasamaK]

For this to work, you need accurate locations/ranges. I have implemented this myself in my VS Code extension for some of the simple rules, but it doesn't always work as expected due to inaccurate location reporting.

Blockers: #570, #522