| I guess either way would function, but I think I'd rather not have that limitation. My current use case is to run my code through multiple compilers for multiple targets (a couple are GCC based, others are different). I want to merge all of those results into a single report of Compiler Warnings. As long as my number doesn't change, I'm not as worried about what the number is. However, when I'm also running my Windows target twice, once for release and once to get test coverage metrics, I can potentially get duplicate warnings if the root path is part of the check. If the warning otherwise matches (and maybe if the parser matches?, that may already be in the check), identical paths relative to the workspace root (which may not match the reported path from the compiler I suppose) should be able to be treated as one warning since in theory the same change should fix it for however many occurrences exist. |
