Description
Is your feature request related to a problem? Please describe.
Since xmake's VS generator takes over the build process, it doesn't allow the compiler direct communication with the IDE which means SARIF support is not available. SARIF is a recent addition to Visual Studio which lets the IDE receive richer information about build errors and warnings.
Describe the solution you'd like
It would be very convenient to just transparently pass through the SARIF output to the IDE so rich error handling is preserved.
Describe alternatives you've considered
cl.exe can output SARIF information to a file via the /experimental:log build flag, but it requires a distinct file name for each concurrent cl.exe process which makes it tricky to use and even then it does not automatically get picked up by VS.
Additional context
Docs on the feature: https://learn.microsoft.com/en-us/cpp/build/reference/sarif-output?view=msvc-170
I assume VS and msbuild by default use the named pipe approach.