SA1206 firing incorrectly for `required` in C# 11
See original GitHub issueVersion: 1.2.0-beta.435
Repro:
internal struct SomeStruct
{
public required int Prop { get; set; }
}
Expected: No warnings
Actual:
SA1206: The 'required' modifier should appear before 'public'
Issue Analytics
- State:
- Created a year ago
- Reactions:23
- Comments:11 (7 by maintainers)
Top Results From Across the Web
StyleCop Rules Documentation
The StyleCop tool provides warnings that indicate style and consistency rule violations in C# code. By default, the tool integrates into Visual Studio...
Read more >All Info - S.1867 - 112th Congress (2011-2012): National ...
Levin, Carl [D-MI] (Introduced 11/15/2011) ... 612) Requires hostile fire and imminent danger pay and hazardous duty pay to be prorated according to...
Read more >Monongahela Power v. Public Service, 166 W. Va. 423
Electric utility appealed from a final order of the Public Service Commission allowing utility an approximate $5 million rate increase. Remanded ...
Read more >Congressional Record
The Senate met at 9:30 a.m. and was called to order by the Honorable RAND. PAUL, a Senator from the State of Ken-...
Read more >Congressional Record
The Senate met at 9 a.m. and was called to order by the Honorable TINA. SMITH, a Senator from the State of. Minnesota....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s a bit complicated. I need to update dotnet/roslyn-sdk so we can update that dependency, but that work has been blocked on updates to microsoft/vs-extension-testing. Hopefully back in a good state soon.
@Malgefor, there is a pull request prepared, but we are having problems with a bug in the Roslyn version needed to add tests for this change. I have created #3580 to (as a first step) just update the Roslyn version with suggestions on how to temporarily handle the Roslyn bug.
How do you want to handle this, @sharwell?