These can be used to quantify parsing improvements from a change.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
As mentioned offline, we may want a length-weighted version of the ambiguity metric when prioritizing, but I think this one is easier to understand in isolation. If we end up preferring the weighted version we can change this.
Comment Actions
Would it make sense to expose this tool run + statistics as a library. This would help share the code for all the metrics with google3 (as we wanted to keep these metrics in both the places).
Comment Actions
Landed the patch. Will extract this as a library to share this with other continuous evaluation pipeline.