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
I would like to congratulate the team on a fantastic work that has been done both on VSCode and on the amazing cpptools. I’ve been playing with it in a large code base and so far I think it works great. One feature I do find lacking is the “find references” for symbols in the code. Is this feature planned? is there a rough estimate for when will this feature be made available? I guess this would part of the language server. Clangd actually doesn’t provide find references as well, I guess it’s a tricky feature to implement.
Thank you very much for your great work, you have done a marvellous work! Thank you in advance for any information any of you guys can provide on this matter.
Cheers,
Filipe
The text was updated successfully, but these errors were encountered:
Yes, find all references is our most up-voted feature: #15 is the issue tracking this. We plan to implement the feature but we don't have an estimated timeframe.
Thank you very much! I tried to search for an issue that already traced this but I failed to find it. Sorry for the entropy :). I will close this issue then
Hi VSCode team
I would like to congratulate the team on a fantastic work that has been done both on VSCode and on the amazing cpptools. I’ve been playing with it in a large code base and so far I think it works great. One feature I do find lacking is the “find references” for symbols in the code. Is this feature planned? is there a rough estimate for when will this feature be made available? I guess this would part of the language server. Clangd actually doesn’t provide find references as well, I guess it’s a tricky feature to implement.
Thank you very much for your great work, you have done a marvellous work! Thank you in advance for any information any of you guys can provide on this matter.
Cheers,
Filipe
The text was updated successfully, but these errors were encountered: