-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review compiler errors/warnings to identify candidates for code fixes #23326
Comments
Sounds like a good candidate for The great big C# and VB fixer upper challenge. |
I don't know if this is helpful but here you can find an Excel sheet with all C# compiler errors (extracted from ErrorCode.cs). I joined the CSharpResources.resx to get a description and looked up the corresponding github.com/dotnet/docs/tree/master/docs/csharp/language-reference/compiler-messages markdown file. I have also binged the error code like this site:stackoverflow.com cs1503 and took the number of matches as a score how often the error troubles customers. This sheet was created via a PowerQuery script but because it contains a bing API key I only published the raw data. |
These are sorted by ID, but we can use the priority from the spreadsheet as the order to actually file issues. Errors
Warnings
Other
|
@sharwell That list is very nice, but it's a bit empty. Do you think it would be a good idea to put that somewhere in the Roslyn repo as a markdown file (maybe /docs/ide) so that anyone could contribute to it, either by linking to an issue they created or a code fix? Perhaps that file could also link to the spreadsheet. |
Closing as speculative. |
We should enumerate all current diagnostics (errors/warnings) produced by the C# and VB compilers, and identify candidates for code fixes.
Filed in response to #23323, but definitely not the only time it's come up for me.
@gafter @kuhlenh
The text was updated successfully, but these errors were encountered: