-
-
Notifications
You must be signed in to change notification settings - Fork 648
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
[display] Goto Implementation #9043
Comments
BTW I just checked how TypeScript employs this feature and it does exactly what I described here, so I guess that was the indeed the intent. |
@RealyUniqueName Do you remember if |
I think, we can't rely on it for display. |
This indeed looks like it could be solved by using the statistics module with a different filter function afterwards. I can work on the Haxe side, but as usual I'm unable to compile vshaxe so somebody else has to set that up. |
* [display] reorganize statistics a bit * [display] extend reference finding to parent/child fields see #9044 * [display] always walk up the chain to find overrides * [display] collect interface field implementations transitively * [display] consider subclasses transitively as well * [display] and make implementation relations transitive too * [display] add display/implementation see #9043 * [display] add GotoImplementation * [display] speed up implementation finding
Language Server Protocol (and VS Code) supports "Goto Implementation" feature. While I'm not sure what exactly it was designed for, to me it looks like something that could be used for the following things:
From the compiler standpoint to me this looks similar to "find references", so maybe it's not very hard to implement?
I can see this feature being very handy for us at @innogames, because we have quite an inheritance-heavy codebase and we often need to get an overview of what's going on across class hierarchies.
The text was updated successfully, but these errors were encountered: