You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Most editors don't provide decent IntelliSense for imported named modules in C++, especially when it comes to remote packages, as for which accessing and indexing those declarations through different build systems and package managers could be tricky.
Describe the solution you'd like
However, a compromise can be made, to create some sort of compatibility. We can generate a header file that includes all the class declarations of the libraries used, function declarations and so on, as a by-product of the processing of modules. The file may look like this:
Is your feature request related to a problem? Please describe.
Most editors don't provide decent IntelliSense for imported named modules in C++, especially when it comes to remote packages, as for which accessing and indexing those declarations through different build systems and package managers could be tricky.
Describe the solution you'd like
However, a compromise can be made, to create some sort of compatibility. We can generate a header file that includes all the class declarations of the libraries used, function declarations and so on, as a by-product of the processing of modules. The file may look like this:
And it's simple to undefine the macro when actually building our targets, so we can safely
#include
this file in our source files.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: