-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Go to Definition on a #include path doesn't use the IntelliSense info #2564
Comments
It looks like this will be fixed via invoking the new |
@bobbrow Users are frequently hitting this . It makes them think their project isn't configured correctly when it is. See all the linked issues. |
We should move this into the next release then. |
This works, but may be too slow at times. Sometimes it takes 30 seconds to jump into correct header. Is anything being done about IntelliSense performance? |
This issue is fixed in 0.28.0. |
It should go to the definition that is actually being used by the current translation unit (i.e. not showing all the files that match the include path).
The text was updated successfully, but these errors were encountered: