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 does not work correctly with delegate and operator #36377
Labels
Area-Compilers
Area-IDE
Bug
Developer Community
The issue was originally reported on https://developercommunity.visualstudio.com
IDE-Navigation
Navigation and search
Projects
Milestone
Comments
vatsalyaagrawal
added
the
help wanted
The issue is "up for grabs" - add a comment if you are interested in working on it
label
Jun 13, 2019
sharwell
added
the
Developer Community
The issue was originally reported on https://developercommunity.visualstudio.com
label
Nov 21, 2019
@jcouv The above crashes for me in Debug VS. I'm using: Crash is in this stack:
This is the assert that is failing: Conversion.ConversionKind is ExplicitUserDefined. Can you ptal? |
Thanks for the info. Looking |
jcouv
removed
the
help wanted
The issue is "up for grabs" - add a comment if you are interested in working on it
label
Feb 1, 2023
This still crashes. That seems bad, given the simplicity of the code :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area-Compilers
Area-IDE
Bug
Developer Community
The issue was originally reported on https://developercommunity.visualstudio.com
IDE-Navigation
Navigation and search
VSF_TYPE_MARKDOWNVS2019 goes to the operator definition when I perform "Go to Defenition" on "Foo.Test", but I expect it to show me the method "Test"
This issue has been moved from https://developercommunity.visualstudio.com/content/problem/587895/go-to-definition-does-not-work-correctly-with-dele.html
VSTS ticketId: 901152
These are the original issue comments:
Visual Studio Feedback System on 5/29/2019, 11:39 PM (13 days ago):
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
These are the original issue solutions:
(no solutions)
The text was updated successfully, but these errors were encountered: