Skip to content

Changes to header files are not reflected in dependent translation units #1501

@killerkalamari

Description

@killerkalamari

Quite often, I'll manually refactor a header file or source file, and there will be a bunch of "Problem"s listed at the bottom, but then I'll compile and the compile will be successful. Well, the compile could be too permissive, right? However, I've discovered that, whether I compile or not, if I close the folder (or workspace), and then reload it, then the extension will notice that everything's actually fine (the errors are no longer there after the load). Conversely, I might make a change that results in a compile error, and it doesn't catch it, until I reload. I speculate that it is simply not noticing all the changes I'm making and so it misses chances to update the Problems list. I tend to run with a couple windows open (one for each monitor), so I don't know if that is involved.

I'm confident that eventually these problems will be fixed, but in the meantime I'm wondering how hard it would be to add in a command (with hotkey) that I can press periodically to have it refresh the Problems list without having to close and reload all the time. Thanks!

VS Code 1.19.3
C/C++ extension 0.14.6
Ubuntu (64-bit)

Metadata

Metadata

Assignees

Labels

Language ServicebugfixedCheck the Milestone for the release in which the fix is or will be available.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions