Our C/C++ extension has a bunch of known bugs with invalid IntelliSense errors due a different compiler being used, but Copilot is being temporarily mislead to believe it's a "compilerError", due to this Copilot diagnostic tagging code below and the lack of it being sent the diagnostic "source" (our current "source" is "C/C++" but I attempted to fix it by changing it to "C/C++ IntelliSense, but Copilot doesn't see that still). Copilot may be able to determine the source from the error text itself given knowledge of what errors the compilers produce, but it's theoretically possible for some error text to be identical without the "source" to differentiate and seems like it could potentially waste tokens.
|
<Tag name='compileError'> |
A potential fix might just be to add the vscode.Diagnostic source to the context.
...and maybe the "compilerError" text should also be renamed to something less specific and not potentially incorrect.
Our C/C++ extension has a bunch of known bugs with invalid IntelliSense errors due a different compiler being used, but Copilot is being temporarily mislead to believe it's a "compilerError", due to this Copilot diagnostic tagging code below and the lack of it being sent the diagnostic "source" (our current "source" is "C/C++" but I attempted to fix it by changing it to "C/C++ IntelliSense, but Copilot doesn't see that still). Copilot may be able to determine the source from the error text itself given knowledge of what errors the compilers produce, but it's theoretically possible for some error text to be identical without the "source" to differentiate and seems like it could potentially waste tokens.
vscode/extensions/copilot/src/extension/prompts/node/inline/diagnosticsContext.tsx
Line 94 in c2f5cea
A potential fix might just be to add the vscode.Diagnostic source to the context.
...and maybe the "compilerError" text should also be renamed to something less specific and not potentially incorrect.