confusing message: "Squiggles are disabled for this translation unit ..."

[xmnboy]

The warning/error message:

#include errors detected. Please update your includePath. Squiggles are disabled for this translation unit ...

is confusing.

The part about Squiggles are disabled... doesn't make sense because you are looking at squiggles underneath the include file that cannot be found!!

After some head scratching, I realized that what you are trying to say is that "Squiggles are disabled for the rest of this file until all #include errors have been resolved."

I'm sure there are other ways to say this, but the current wording seems contradictory. 😄

[Colengms]

Hi @xmnboy . Thanks for reporting this. We'll look into updating this string.

[sean-mcmanus]

I could change the string to explicitly says "IntelliSense error squiggles" to avoid confusion with clang-tidy squiggles as well.

"rest of this file" isn't entirely either accurate because they're actually disabled for the entire TU, including potentially previous lines of code and/or in header files.

[xmnboy]

@sean-mcmanus -- I don't think user's will know there is a distinction between Intellisense squiggles and clang-tidy squiggles, it will all appear to be Intellisense to them. Maybe something like:

Intellisense processing of this file is disabled until #include errors are resolved.

[sean-mcmanus]

clang-tidy squiggles have a clang-tidy error code string and will usually be warning instead of errors while IntelliSense squiggles have a numeric error code (currently undocumented, but eventually we may be able to have links with IntelliSense error code documentation), so we're hoping that difference will make the 2 types of error sources understandable, but we could also potentially add "IntelliSense" or "clang-tidy" to the "C/C++" source string:

[bobbrow]

What if we just use the common term "linting" and just say that "linting will be disabled for this file"?

EDIT: IntelliSense in the broader sense is not disabled for these files. We're just not confident that it will be very accurate when #include statements don't resolve.

[sean-mcmanus]

@bobbrow clang-tidy does linting (additional checks that aren't strictly compiler errors), but IntelliSense doesn't really do linting (just compiler errors), and clang-tidy's linting may not be disabled. "IntelliSense errors" are disabled.

[xmnboy]

How about:

Additional error processing of this file is disabled until #include errors are resolved.

[CanDursun]

This is happening to me too.

[sean-mcmanus]

@CanDursun This issue is just in regards to improving the error message. If you're having an issue with resolving headers you should open a new issue or discussion.