Rust: Add expressions with known type metric #20670
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add missing metric "expressions with known type" to
rust/telemetry/extraction-information. I say missing because this metric is expected by the default DCA summaries and we've been getting warnings in Rust runs because it was missing.Perhaps more controversially, I've also added the same metric to
rust/diagnostic/database-quality(i.e. the query which feeds tool status page), since that's easy to do and aligns Rust more closely to other languages such as Java. I have set a very low threshold for the new metric here, for the time being, as I don't want to draw too much attention from the existing issues identified by the tool status page (that are being worked on). With the low threshold, 15 projects on the MRVA-1000 trigger the new condition, but only 1 of those wasn't already triggering another condition of the query anyway.