… accessors had no references

…he comment more comprehensive

All array types for one elemnt type is consider same in our index.
e.g. int[], int[][] and int[,] are just represent as int[]

…reeInfo

Since they are already from the same compilation that triggered completion.

…emantic diagnostics for a specific tree, which are categorized by each analyzer that reported the diagnostic. We have existing APIs on this type that return the same diagnostics, but as a single group instead of categorized by analyzer. Latter is required by the IDE analyzer host as we cache diagnostics from each analyzer.

First step towards #44408

1. Refactor IDE open file analysis so that we have a single place where we execute the analyzers for document analysis. I have preserved the existing IDE layer diagnostic caching in this PR, but it should hopefully go away in future when we move the diagnostic computation to OOP.
2. Perf improvement: Currently, we execute open file analyzers one at a time by making separate calls into CompilationWithAnalyzers. This identified overhead where we are recomputing lot of stuff with each call and missing semantic model/bound node cache hits. This PR simplifies the approach by invoking a single syntax/semantic call into CompilationWithAnalyzers with all relevant analyzers. This required adding a new public API to CompilationWithAnalyzers to return syntax/semantic diagnostics for a tree/model grouped by analyzers, which has been split into a separate commit.
3. Remove code for code fix support for CompilationEndAction diagnostics - these actions are not executed in the IDE live analysis, so the code was not executing. Additionally, we have identified that we never want to run these actions in IDE live analysis due to associated perf concerns.

Future steps:
1. Move open file diagnostic analyzer execution to OOP
2. Remove IDE layer diagnostic caching, and rely on caching at OOP side
3. Investigate moving even compiler diagnostic computation to OOP - need to ensure responsiveness of refreshing compiler diagnostics on typing is not affected

…ument analysis

…emantic diagnostics for a specific tree, which are categorized by each analyzer that reported the diagnostic. We have existing APIs on this type that return the same diagnostics, but as a single group instead of categorized by analyzer. Latter is required by the IDE analyzer host as we cache diagnostics from each analyzer.

A workspace can customize which changes are allowed to be applied
through TryApplyChanges. There's a CanApplyChanges that generally
is called with each type of change which you can opt in for. There is
also a specific overloads for filtering specific changes to
CompilationOptions or ParseOptions, since a host may support changing
some of those but not all of them.

This documents our existing behavior and adds tests to confirm the
behavior. There were some Debug.Asserts() that are incorrect and are
now fixed.

…onError

Fixes #45452

…cumentChangedAsync

Include line numbers in Integration Test stack traces

* Introduce LanguageVersion.CSharp9
* Limit netcoreapp3.0, 3.1 and netstdard 2.1 to C# 8.0
* Map CSharp9 to language version preview
* Default to CSharp9 for netcoreapp5.0
* Add Tests

…45374)

Perf improvement for completion of unimported extension methods

Fix inconsistencies in handling CompilerVisibleItemMetadata

* Additional tests for nested function contexts.
* Override VisitFunctionPointerLoad in MethodToClassRewriter.
* Adjust debug asserts.

…records.

…626.2 (#45482)

Microsoft.DotNet.Arcade.Sdk
 From Version 1.0.0-beta.20302.3 -> To Version 1.0.0-beta.20326.2

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

We have two members in TypeKind that point to the same value, Struct
and Structure. Because of this, Enum.ToString(), which under the covers
uses a binary search, isn't stable which one it will pick and it can
change if other TypeKinds are added. This ensures we keep using the
same string consistently.

We also have a few members in MethodKind that are also duplicates, but
it appears those have kept stable. To be safe, we now serialize
explicitly.

Fixes #44714

Reduce memory required for document change processing queues

Update Language Feature Status

…nsistency

Fix up nondeterminism in serializing naming style preferences