Tested with `-checks=level1,level2,level3 -export-fixes=/tmp/clazy-fixes.yml -enable-all-fixits /home/chgans/Projects/navico/NS/nos/UI/tBlankScreen.cpp`, here is an output excerpt:
```
- DiagnosticName: clazy-qstring-allocations
Message: 'QString(const char*) being called'
FileOffset: 21477
FilePath: /home/chgans/Projects/navico/NS/nos/UI/tBlankScreen.cpp
Replacements:
- FilePath: /home/chgans/Projects/navico/NS/nos/UI/tBlankScreen.cpp
Offset: 21495
Length: 0
ReplacementText: 'QLatin1String('
- FilePath: /home/chgans/Projects/navico/NS/nos/UI/tBlankScreen.cpp
Offset: 21507
Length: 0
ReplacementText: ')'
```
There's currently 2 major issues:
- `FixItExporter::ConvertFixIt` will screw up if macros are involved, shouldn't be hard to fix
- If passing `-export-fixes` and several translation units, the exported file will be overwritten for each translation unit. I have to check how clang-tidy deals with this, but my feeling is that we should refuse to start in that case or we'll need to be able to aggregate ` clang::tooling::TranslationUnitDiagnostics`, and this will have to be done outside the exporter, since a new context is created for each input to process
A minor issue is the handling of old vs new style to manage replacement, for now the code does one or the other, but doesn't warn or fail if both are request from the command line.