- Don't do analysis for speculative attributes
- Manually call TryGetThisParameter, rather than MethodThisParameter which can throw

- Add an entry point to nullable walker for attribute analysis
- Implement analyze attribute in the walker
- Remove the analysis from binder_attributes and call nullable walker instead
- Add extra fields to BoundAttribute that are needed for nullable analysis
- Add some extra test scenarios

- Support supression
- Fix params array of null
- Fix arguments out-of-order

- At binding time check both constructor and value arguments for const null
- When arguments are arrays, check for nullable array mismatch
- When arguments are non nullable arrays check for nullable inside initializers
- Add tests

* Update dependencies from https://github.com/dotnet/arcade build 20190308.5

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19158.5

* Update dependencies from https://github.com/dotnet/arcade build 20190309.2

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19159.2

* Update dependencies from https://github.com/dotnet/arcade build 20190310.1

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19160.1

* Update dependencies from https://github.com/dotnet/arcade build 20190310.2

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19160.2

* Update dependencies from https://github.com/dotnet/arcade build 20190311.14

This change updates the following dependencies
- Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19161.14

we want to move to newer version of JsonRpc (2.x) from 1.x we use.

but that has some complexity since version 2.x and 1.x is incompatible and we let partner to directly access Rpc exposed from ServiceHubServiceBase type.

this is first step so that partners move to new API that doesn't expose JsonRpc directly.

once they moved, moving us to new versino should be easier since we will not break partner teams.

Fixing false unresolvedConflict when renaming overloaded VB properties

Fixes #33783

Ref and out parameters with suppression should change the nullable state
for the argument being suppressed. Moreover, the changes should flow
through type inference.

Closes #27743

Fix local bootstrap build

Merge dev16.0 to master

Merge dev16.0 to master

Have to disable quiet restore explicitly on local dev machines when
doing a bootstrap build to work around this arcade issue:
https://github.com/dotnet/arcade/issues/2220

Check nullness of a nullable receiver when invoking base methods.

Fix stack overflow compiling deeply nested generic

Nullable nontrivial constructor should propagate state of the argument to Value.

* Correct parsing of a parenthesized constant pattern expression in switch expression arm
Fixes #33675
* Add a test that we properly bind and code-gen a parenthesized constant expression.

handle extension methods in "Sync Namespace" refactoring

Did some profiling and all of the slowness is due to peverify. It seems
to hit a wall about 700 levels of nesting. Once it's removed we can
easily test our tolerance levels in the compiler

* Implement LDM decisions on the behavior of `??` and `??=` operators
Fixes #33743

* Update CoreFX dependencies

* Generate suggested binding redirects

Wait for graceful close before terminating process

As a part of implementing nullable reference types many of our locals
switched from `TypeSymbol` to `TypeSymbolWithAnnotations`. In the vast
majority of cases this doesn't have a meaningful impact on compilation.
They are bigger (about 3X) but it's still a relatively small `struct`
(three words).

The size difference is significant though in
`BindNamespaceOrTypeOrAliasSymbol`. This method is used in recursive
parts of binding and is mutually recursive with `BindQualifiedNam`. This
method defines a large number of locals which contribute to every layer
of recursion. When they moved to `TypeSymbolWithAnnotations` this pushed
us outside our tolerance levels and we hit an overflow in extreme cases.

Virtually none of these locals are used in the recursive case. Factored
their use into local functions so we only pay the stack usage on demand.

closes #33909
fixes https://github.com/dotnet/coreclr/issues/22757

Pass NoBuild=true to Publish step

Bases of Nullable are reference types and thus base methods are called via boxed values which wold NRE on nulls.

Fixes:#33174