Integrating class symbol support - #1984
Conversation
82ec11f to
604d6a7
Compare
Andy Jordan (andyleejordan)
left a comment
There was a problem hiding this comment.
Some quick comments but there's more, I just need to eat lunch.
|
This is coming along very well! I'll try to consolidate my thoughts in this PR 🙂
|
|
Latest commit fixed the reference-issue with large files 🎉 I've updated the previous post |
Since `FindReferencesOfSymbol` is already used.
This required using a `ScriptFile` for the associated test in `AstOperationsTests`. The coupling of the visitor to the file seems fine since that's the _point_ of this improvement: a cached sets of references for each file. We also have to carefully sort our list of symbol references for things that expect them in order.
| { | ||
| Label = parameterInfo.Name, | ||
| Documentation = string.Empty | ||
| Documentation = parameterInfo.HelpMessage |
There was a problem hiding this comment.
Patrick Meinecke (@SeeminglyScience) Not a whole lot comes from this it seems.
So that we rely on the dictionary to sort our symbols into the equivalent types instead of having to perform a filter.
I think there's a cleaner way to do this, but this works.
Against the full name and not just the identifier, since it's what's displayed in the search menu. Now you can search methods by their parameters' names.
Should have been just `IndexOf`, and also use `+` instead of `string.Concat()` for simplicity and speed.
|
Thanks Frode Flaten (@fflaten) and Patrick Meinecke (@SeeminglyScience), resolved those things! |
Patrick Meinecke (SeeminglyScience)
left a comment
There was a problem hiding this comment.
LGTM! These changes are awesome. Huge thank you Frode Flaten (@fflaten) (and ofc Andy Jordan (@andschwa)) ❤️







This is the full (admittedly still a bit of a work-in-progress PR) that integrates #1886 into
main.