Enable module-wide symbol indexing and operations

[daviwil]

We need to have a more robust and reliable method for indexing symbols across a module or modules within a workspace so that the following operations work as expected:

• Go to definition
• Find all references
• Rename symbol

[TylerLeonhardt]

Did you make any progress on this one?

[daviwil]

Nope, never had time. One thing I wanted to do was to create a "Project" subsystem for PSES which is able to index files in a way that will be semantically correct for the language and really efficient. It is a nontrivial amount of work. Maybe @SeeminglyScience might want to look into it someday ;)

[SeeminglyScience]

Coincidentally I've thought about this a lot over the last month or so. I think an ideal implementation would be being able to select a target psd1 file the same way the C# extension can select a target csproj.

Unfortunately even with that system, this is way more complex than it may seem on the surface. Ideally, this would work purely from static analysis. Realistically, we'd either have to enforce a standard way of loading functions from separate files or load the module and operate based on the state. And I have a hard time seeing the former as a real possibility.

Actually executing the module is the only way I see this working reliably but I think there are a lot of non-technical challenges with that. You'd have to communicate clearly that the simple act of opening a workspace might execute code, and it'd definitely have to be opt-in only.

I think workspace profiles are a really good first step into that space, and I wouldn't put too much time into thinking about this feature until that's implemented.