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
{{ message }}
Repository navigation
Code completion does not work within Lambda expressions #1943
There is a known issue in which lambda expression aren't given access to the private members when they should (inherited from Visual Studio...the bug has existed for 4 years, so I don't think they're fixing it soon). Public variables/methods autocomplete, right? That's what I'm seeing. If not, it's some other bug. We could work around this issue by skipping all the "is this accessible" checking (i.e. incorrectly showing inaccessible private data when we shouldn't) or find some way to implement a Show More Results completion option like VS has (I don't think VS Code has a UI mechanism for this yet though).
We've implemented the 2nd Ctrl+Space invoking "show more results" as a workaround for this (for our next release, #2386 ), but the root bug hasn't been fixed.
Steven.Xi (@stevenxi) Completion providing is language dependent with a different C# implementation, so the C# issue is unlikely to share the same root cause as the C++ issue (for VS or VS Code), i.e. you'd want to file a different bug for VS 2019 for C# (if it doesn't exist already).
Activity
sean-mcmanus commentedon May 7, 2018
There is a known issue in which lambda expression aren't given access to the private members when they should (inherited from Visual Studio...the bug has existed for 4 years, so I don't think they're fixing it soon). Public variables/methods autocomplete, right? That's what I'm seeing. If not, it's some other bug. We could work around this issue by skipping all the "is this accessible" checking (i.e. incorrectly showing inaccessible private data when we shouldn't) or find some way to implement a Show More Results completion option like VS has (I don't think VS Code has a UI mechanism for this yet though).
lh123 commentedon May 7, 2018
Yes, public variables/methods autocomplete working properly，but private members doesn't work.
lh123 commentedon May 7, 2018
I think we can use press
ctrl+spacetwice or three times to triggerShow More Results.sean-mcmanus commentedon May 7, 2018
Yeah, I think that would be doable. I think the fix should be pretty easy, but I'm not sure when it'll get on our schedule yet.
sean-mcmanus commentedon Aug 11, 2018
We've implemented the 2nd Ctrl+Space invoking "show more results" as a workaround for this (for our next release, #2386 ), but the root bug hasn't been fixed.
Colengms commentedon May 1, 2020
I happened across this same issue and opened (another?) bug against VS, here: https://developercommunity.visualstudio.com/content/problem/1007155/intellisense-in-a-lambda-auto-complete-does-not-su.html
stevenxi commentedon Jun 2, 2020
I believe I'm experiencing similar problem, but with C#
Maybe it's a general VS 2019 problem?
sean-mcmanus commentedon Jun 2, 2020
Steven.Xi (@stevenxi) Completion providing is language dependent with a different C# implementation, so the C# issue is unlikely to share the same root cause as the C++ issue (for VS or VS Code), i.e. you'd want to file a different bug for VS 2019 for C# (if it doesn't exist already).
Colengms commentedon Nov 15, 2024
This appears to have been addressed at some point, as it doesn't repro with the latest version (1.23.1):
Closing as fixed.