@@ -51,3 +51,19 @@ Each entry should include a short description of the break, followed by either a
6. https://github.com/dotnet/roslyn/issues/37527 The constant folding behavior of the compiler differed depending on your host architecture when converting a floating-point constant to an integral type where that conversion would be a compile-time error if not in an `unchecked` context. We now yield a zero result for such conversions on all host architectures.
7. https://github.com/dotnet/roslyn/issues/38226 When there exists a common type among those arms of a switch expression that have a type, but there are some arms that have an expression without a type (e.g. `null`) that cannot convert to that common type, the compiler improperly inferred that common type as the natural type of the switch expression. That would cause an error. In Visual Studio 2019 Update 4, we fixed the compiler to no longer consider such a switch expression to have a common type. This may permit some programs to compile without error that would produce an error in the previous version.
8. User-defined unary and binary operators are re-inferred from the nullability of the arguments. This may result in additional warnings:
// Copyright (c) Microsoft. All Rights Reserved. Licensed under the Apache License, Version 2.0. See License.txt in the project root for license information.