Warn on analyzer crashes in runtime repo

[marek-safar]

Trimming analyzers are complex and we don't have comprehensive code coverage for them right now. We should enable them for whole runtime repo to catch problems like dotnet/linker#3046 earlier.

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Trimming analyzers are complex and we don't have comprehensive code coverage for them right now. We should enable them for whole runtime repo to catch problems like dotnet/linker#3046 earlier.

Author:	marek-safar
Assignees:	-
Labels:	area-Infrastructure-libraries, untriaged
Milestone:	-

[vitek-karas]

@tlakollo @sbomer - I think they're enabled - at least looking at binlog locally they're in the list of analyzers and they're enabled. I didn't try to break it to get it to warn, but I know this worked last time I played with trimming annotations in the runtime repo.
That said - the above issue is from runtime repo - so I guess I don't know.

[sbomer]

Yes, they're enabled on dotnet/runtime but crashes usually aren't usually surfaced because they turn into AD0001 warnings which runtime hides. See dotnet/linker#2847 (comment).

[ViktorHofer]

Moving to meta as there is no infrastructure work needed.

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Trimming analyzers are complex and we don't have comprehensive code coverage for them right now. We should enable them for whole runtime repo to catch problems like dotnet/linker#3046 earlier.

Author:	marek-safar
Assignees:	-
Labels:	area-Meta
Milestone:	8.0.0

[ericstj]

Remaining work here is to turn on AD0001 as a warning and see if we are clean. IMO this is OK to do - if it becomes a problem we NoWarn it in the faulting project and file an issue.