It looks like method group conversions apply regular method overload resolution when resolving target method group.
However we know that in such scenario, unlike the regular argument passing, "byval" cannot match "in".

We should reject candidates with in/val mismatches when doing overload resolution for group conversion purposes. Otherwise we may encounter false ambiguity errors or even pick wrong candidates that crash at run time.

Fixes:#23319

Handle an empty span for 'introduce variable' refactoring

Provider a user option to enable/disable the 'Use auto property' analyzer

Enabled 'Use Local Function' refactoring for delegate which is invoked with Invoke

Escape keyword argument names in 'add argument name' refactoring

Fixes #23351.

Fix for #22690 NRE in GetAttributeSyntaxNodeOfToken in AbstractInternalsVisibleToCompletionProvider

Delete legacy deferred solution support

Correcting a possible copy and paste error, should be `FULLWIDTH_LATIN_SMALL_LETTER_B`.

Extended integer prefix tests to cover full range of permitted characters.

Revert "Disable autosign of SWIX projects"

Add a -binaryLog option to build.cmd / ps1

Fixes #12214

Ensure the operand of an is-pattern expression is evaluated.
Fixes #22619

This reverts commit ce4496ab.

Can now specify "-binaryLog" to Build.cmd and it will produce a binary
log for every invocation of MSBuild. The logs will be written out to the
`Binaries\Logs` directory.

Fixes #23282.

* VB EE: Properly handle syntax errors in synthesized assignments

* Fix test

Get compiler status doc updated for 7.3

Moving the C# 7.1 and 7.2 releases further down the status document. They are
shipped, no longer in active development and hence likely of less interest to
readers looking at active feature status.

Enable publishing of the vs-for-mac packages

Move VS insertion item after signing

Change the 'Use auto property' code fixer to not be a 'compilation end' analyzer.

The VS insertion items require a bit more work to be a part of batch
signing. In particular the VSMAN files because they contain checksums of
many of our other assets. These need to be rewritten during batch
signing to have the new correct values.

These assets though aren't actually required to be signed though. Hence
for now just moving the building of them till after signing completes.

when OOP is killed by users, default(DesignerAttributeResult) is returned. it was okay when it was class, but not it being struct, it cause issue because NotApplicable return false rather than true in error case.

so, change NotApplicable to Applicable so that it can handle the error case better.

Mop up merge of post-dev15.5-contrib to master

Workaround for test SDK issue Microsoft/vstest#373