Skip to content
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

the result of peek declaration is not the same to go to declaration #2671

Closed
alianZhen opened this issue Oct 15, 2018 · 2 comments
Closed

the result of peek declaration is not the same to go to declaration #2671

alianZhen opened this issue Oct 15, 2018 · 2 comments
Labels
Language Service more info needed The issue report is not actionable in its current state not reproing We're not able to reproduce the issue (it's unlikely to get fixed until we find one).

Comments

@alianZhen
Copy link

Go to declaration now is perfect!

But the result of peek declaration is not the same to go to declaration,can make their result the same?

@bobbrow bobbrow added Language Service investigate This issue needs to be investigated/confirmed labels Oct 15, 2018
@sean-mcmanus sean-mcmanus added more info needed The issue report is not actionable in its current state not reproing We're not able to reproduce the issue (it's unlikely to get fixed until we find one). and removed investigate This issue needs to be investigated/confirmed labels Oct 18, 2018
@sean-mcmanus
Copy link
Collaborator

How do I repro this?

@michelleangela
Copy link
Contributor

Closing this issue. If you update to the latest version of the C/C++ extension and your issue still persists, please re-open the issue and reply with additional information that can help us investigate the issue.

@github-actions github-actions bot locked and limited conversation to collaborators Oct 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Language Service more info needed The issue report is not actionable in its current state not reproing We're not able to reproduce the issue (it's unlikely to get fixed until we find one).
Projects
None yet
Development

No branches or pull requests

4 participants