Fixes #9576

In the C# expander, we added a step to expand return statement expressions within lambda bodies to aid in conflict resolution for refactoring. However, we failed to account for the fact that lambda return statements can legally have no expression. A simple null-ref is all that's necessary to fix the crash.

Note: This bug was introduced (by me!) in #6432. It was not included in Update 1, so this is a newly-introduced regression in Update 2.

Fixed race in diagnostic tagger

Non-Fatal Watson if ReiteratedVersionNumber matches when text does not.

change telemetry reporting for rename

Only log formatting events in telemetry when they are enacted by the …

Fix crash if client completes the event queue before the compiler is finished with it.

Allow null Compilation in SymbolDistinguisher.Description.GetHashCode

Disable diagnostic service for projects that we know we don't have all information to provide good results.

Revert "Revert "Disable diagnostic service for projects that we know we don't have all information to provide good results.""

Port analyzer allocation fixes from master to stabilization

Fix race condition when generating simulated compilation events

Include HasValue check in BoundSwitchStatement

If the switch expression is a  Nullable<T>  a conditional branch is added for the  HasValue  check.
 That check was added as a separate  BoundStatement  outside of the  BoundSwitchStatement .
 If the lambda rewriter subsequently generated any display class instances, the allocations are added
 as a prologue to the rewritten switch statement but since the conditional branch is outside the switch
 statement, the branch skips the prologue, skipping the allocations. The change is to include the
 conditional branch in the  BoundSwitchStatement  so the branch occurs after the prologue.

[AskMode] Put `IOperation` behind a feature flag

don't assume all reference spans in an inline rename session are projected into the current view

Check file checksums to ensure no corruption occurred.

Include HasValue check in BoundSwitchStatement so any display class allocation is moved outside of the check

allow cancelation exceptions through the PE stream diagnostic filter

User scenario: Analysis might get skipped in the IDE for a symbol/partial declarations for a partial symbol with more than one definition in a single document.

Cause: When computing symbols declared in the tree to generate symbol declared events, we were adding duplicate entries if a symbol had more than one partial declaration in a tree. This meant that multiple threads might start performing symbol analysis on the same symbol, causing a race condition as driver doesn't expect duplicate events. Though we ensure not to make duplicate callbacks, we might end up missing on making some callbacks at times.

Fix: Compute only unique symbols from declarations in a tree.

Risk: None, it is a trivial fix.

Testing: Before the fix, I was able to repro the race condition and the assert consistently by running the flaky test in a loop for over 10k times. After the fix, it doesn't repro on running the same multiple times. A new unit test has also been added, though it did not fail consistently even before the fix.

Fixes #9462

Revert "Disable diagnostic service for projects that we know we don't have all information to provide good results."

Revert "Disable diagnostic service for projects that we know we don't have all information to provide good results."

only report when visual studio closes.

Disable diagnostic service for projects that we know we don't have all information to provide good results.

Port analyzer allocation fixes from master to stabilization (https://github.com/dotnet/roslyn/pull/9327 and https://github.com/dotnet/roslyn/pull/8937)

Fix EnC for compilations with dependencies using time-based versioning

Handles clause with missing MyBase