This extension is great but sometimes it introduces some ambiguity during it's action.
For example you have some source file that includes a bunch of header files. And suppose that you have some error in one of them. Clang static analyser that is used in VS Code doesn't show this sort of errors, and, subsequently, you don't know about it. In this kind of situation code completion by your extension fails to propose any hints (because clang returns some error code) and user sees a list proposed by VS Code basic code completion engine. I ran into this situation many times, and what annoys me even more - that in some files code completion works perfectly, and in other (that have some compilation errors) - it doesn't. And you don't know why.
It would be very convenient if this extension passed clang stderr output into the "extensions OUTPUT console" that is present in VS Code.
Hi.
This extension is great but sometimes it introduces some ambiguity during it's action.
For example you have some source file that includes a bunch of header files. And suppose that you have some error in one of them. Clang static analyser that is used in VS Code doesn't show this sort of errors, and, subsequently, you don't know about it. In this kind of situation code completion by your extension fails to propose any hints (because clang returns some error code) and user sees a list proposed by VS Code basic code completion engine. I ran into this situation many times, and what annoys me even more - that in some files code completion works perfectly, and in other (that have some compilation errors) - it doesn't. And you don't know why.
It would be very convenient if this extension passed clang stderr output into the "extensions OUTPUT console" that is present in VS Code.
Best regards, Max.