Olia Gavrysh

We should invest in 1. "Suppress and perform runtime check" and postpone 2. and 3. cause there is no right APIs to do it.

We will first implement #73 and then reconsider the design for 1. "Suppress and perform runtime check"

What is the scenario you are going for? 1. Do you want to have to exclude false positives? 2. Are you trying to minimize pragma suppressions?

Before closing move from backlog: [ ] #10 [ ] #55 [ ] #71

Confirmed with Roslyn team that IOperetion is already shipped with VS 15.5

This depends on #73, once we implement it, we can do this one.

From Wes Haggard email: "The APIs are present in .NET Core but they aren’t very useful without the rewriting tools. So people can annotate their APIs but someone would need...

After #73 is done we should provide separate warning caption and description for System.Diagnostics.Contracts according to Wes Haggard email in the comment above.

Instead of changing the indexer, we probably should do a manual review of `exceptions.csv` with the respective area owners.

@merriemcgaw is this expected? Should we update docs or create an issue in our repo?