You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
intX=1; // error: struct with field initializers must include an explicitly declared constructor
129
+
publicR(intx) :this(x, 0) { } // ok
130
+
}
131
+
```
132
+
133
+
5. <aname="5"></a><aname="roslyn-57925"></a>InVisualStudio17.0servicing, ifa `struct` typedeclarationwithnoconstructorsincludesinitializersforsomebutnotallfields, thecompilerwillreportanerrorthatallfieldsmustbeassigned. See [roslyn#57925](https://github.com/dotnet/roslyn/pull/57925).
134
+
135
+
Forinstance, thefollowingresultsinanerror:
136
+
```csharp
137
+
structS// error CS0171: Field 'S.Y' must be fully assigned before control is returned to the caller
Copy file name to clipboardexpand all lines: docs/compilers/CSharp/Compiler Breaking Changes - DotNet 7.md
+34-5
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
## This document lists known breaking changes in Roslyn after .NET 6 all the way to .NET 7.
2
2
3
-
1. In Visual Studio 17.1, the contextual keyword `var` cannot be used as an explicit lambda return type.
3
+
1.<aname="1"></a>In Visual Studio 17.1, the contextual keyword `var` cannot be used as an explicit lambda return type.
4
4
5
5
```csharp
6
6
usingSystem;
@@ -13,7 +13,7 @@
13
13
classvar { }
14
14
```
15
15
16
-
2. InVisualStudio17.1, indexersthattakeaninterpolatedstringhandlerandrequirethereceiverasaninputfor the constructor cannot be used in an object initializer.
16
+
2. <aname="2"></a>InVisualStudio17.1, indexersthattakeaninterpolatedstringhandlerandrequirethereceiverasaninputfor the constructor cannot be used in an object initializer.
Copy file name to clipboardexpand all lines: docs/contributing/Compiler Test Plan.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,8 @@ This document provides guidance for thinking about language interactions and tes
2
2
3
3
# General concerns:
4
4
- Completeness of the specification as a guide for testing (is the spec complete enough to suggest what the compiler should do in each scenario?)
5
-
- Other external documentation
5
+
-*Ping* for new breaking changes and general ping for partner teams (Bill, Kathleen, Mads, IDE, Razor)
6
+
- Help review external documentation
6
7
- Backward and forward compatibility (interoperation with previous and future compilers, each in both directions)
7
8
- Error handling/recovery (missing libraries, including missing types in mscorlib; errors in parsing, ambiguous lookup, inaccessible lookup, wrong kind of thing found, instance vs static thing found, wrong type for the context, value vs variable)
0 commit comments