I tried to recreate the issue you described, but it did not produce any parse error.
In order to better understand the situation, could you please create a small test program that triggers the parse error, then generate a reproducer for it?
To generate the reproducer file:
Search in the analysis log for the full path of the source file for which you want to create a reproducer (for instance, here, the file that generates this issue). You will have to use exactly this name (same case, / or \…)
Add the reproducer option to the scanner configuration: sonar.cfamily.reproducer= "Full path to the source file"
Re-run the scanner to generate a file named sonar-cfamily.reproducer in the project folder.
thanks for taking a look at this. I can repro this with a minimal example. Attached is the requested reproducer file. sonar-cfamily.reproducer (750.3 KB)
FYI, we fixed the issue and it should be available in the next release.
In the meantime, to work around the issue, you can add the following to the build command used for analysis: /D"__is_assignable_no_precondition_check=__is_assignable".