Skip to content
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

Enable existing "strict" warnings under /warnversion #45704

Open
3 of 8 tasks
gafter opened this issue Jul 6, 2020 · 1 comment
Open
3 of 8 tasks

Enable existing "strict" warnings under /warnversion #45704

gafter opened this issue Jul 6, 2020 · 1 comment

Comments

@gafter
Copy link
Member

gafter commented Jul 6, 2020

This depends on the completion of #45702. It is part of #45701. This is an umbrella issue to track the work of enabling existing diagnostics that are reported under "strict" mode in warning wave "5". See https://github.com/dotnet/roslyn/projects/10#column-3494327, possibly including the following:

Note: Most of these suggestions are errors rather than warnings when diagnosed in strict mode. We will need to decide whether to downgrade them to warnings (presumably with a new error code) when reporting them in a warning wave, or to permit errors to be reported in a wave.

@gafter
Copy link
Member Author

gafter commented Jul 7, 2020

Some of these are targeting 16.8. Others will be deferred. When we schedule or start work on one, we'll create a work item to track it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants