Improve "Go to all" navigation in VS

It kinda works, but we should look into proper ordering of the results. Example with camel case search: I’d like to navigate to FSharpDiagnosticSeverity so I type FSDS

But I get GuidsArrayFromSemicolonDelimitedStringOfGuids as the first result. Even when the file with a better matching type is the currently active document.

The relevant results are actually present, but only after all the files that match (even barely) the search term:

[majocha]

One improvement I’d love is more aggressive caching. Currently we have a MemoryCache which evicts after 10s or so. IIRC this is a remnant of 32bit VS and fighting for every scrap of memory. In efffect every time you search in a larger solution like VisualFSharp, there’s a lot of churn and it takes quite some time on a slower machine.

For example, there are 97k possible search results in VisualFSharp.sln:

I’d trade that 6MB memory to reduce the carbon footprint of regenerating them on every search 😀.

[psfinaki]

@majocha you are doing an awesome job. As for operator names, IMO we are suffering from a primitive obsession in the relevant code. We have this core name, mangled name, display name - all as basic strings hence all kinds of weird bugs at edge cases, you have caught one of them, there are many in tooltips I think.