this support wasn't there before since code lens nor solution analysis requires it.

Build cleanup

Enable test that is passing now.

Closes #14529.

Remove LINQ allocations from FAR item display logic

Merge thread starvation fix into master

Avoid GUID conflicts for Naming Styles Symbol Specifications (causes Naming Styles to not work and the Tools | Options page to not load)

Do not fail in the NamingStyleCodeFix when we cannot find the symbol (causes the failure InfoBar to be shown)

Don't emit casing-related naming violations when the violating character has no casing (making the feature noisy/unusable in other cultures)

make sure we empty out information in solution/project/documentInfo w…

Ensure that we don't break if we recurse into methods during symbol-key reader

Fixes #16585

Restore detection of an ambiguous method type argument inference.

Expand the lifetime of locals declared within CasePatternSwitchLabelSyntax to the entire switch body.

Fixes #16513

Fixes https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_workitems?id=336030
Fixes https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_workitems?id=294570
Fixes https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_workitems?id=363714
Fixes https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_workitems?id=336030
Fixes https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_workitems?id=364165
Fixes #16296
Also adds test for #16559

This uage of .Select is responsible for 1.3% of allocations if you FAR for SyntaxNode.

Expand the lifetime of locals declared within CasePatternSwitchLabelSyntax to the entire switch body.

Fixes #15536.
Fixes #16066.

Fixes #16478.

Fixes #15326, #15486

Fixes #16431

made venus span mapper to deal with typescript better

make sure we empty out information in solution/project/documentInfo whose ownership is moved to Solution/Project/DocumentState

otherwise, we will keep holding on staled data longer than necessary.

this change makes OOP to consume 300MB less in roslyn size solution.

Add EditorConfig settings for source formatting

Allow extension methods on tuple receivers when underlying conversions are "upcasts"

Fixes #15788

We should always be able to find the symbol that generated this
diagnostic, but this cannot always be done by simply asking for the
declared symbol on the node from the symbol's declaration location.
Issue #16588 is tracking a more complete fix for this that always
successfully finds the symbol.

Fixes #16517 

Merge dev15-rc3 into master

Extensions methods declared on bases and implemented interfaces are allowed to be applied to receivers that of derived or implementing type.

This change extends this rule to tuple receivers as long as the rule holds for individual elements, recursively.

I.E. valid "this" conversions are:
- identity conversion
- implicit reference conversion
- boxing conversion
- (new)  implicit tuple[literal] conversions as long as all underlying conversions are valid "this" conversions.

Move Roslyn dependencies from VSSetup to VSSetup.Dependencies