commit 183fdd0037c36b091eda8538ae99990c88112e3d
author Devon Carew <devoncarew@google.com> Wed Aug 28 16:47:58 2024 -0700
committer GitHub <noreply@github.com> Wed Aug 28 16:47:58 2024 -0700
tree 011eb64e5a370f5bc7aaa07beff369993d6f640b
parent f7191b7a1d07771b3a8a3d2cde0b88b6bbdd6e01

contribute a prompt benchmarking script (#292)

- contribute a prompt benchmarking script

This contributes a contribute a prompt benchmarking script; it gets
label information for ~100 existing issues - assumed to be correctly
labelled - and compares them against the labels predicted by the prompt.
This will allow us to benchmark prompt changes to know whether we're
improving things or not. Note that there are no prompt improvements in
this PR (just some updates for area label changes).

The benchmarking can be re-run via `dart tool/bench.dart`.

---

- [x] I’ve reviewed the contributor guide and applied the relevant
portions to this PR.

<details>
  <summary>Contribution guidelines:</summary><br>

- See our [contributor
guide](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md)
for general expectations for PRs.
- Larger or significant changes should be discussed in an issue before
creating a PR.
- Contributions to our repos should follow the [Dart style
guide](https://dart.dev/guides/language/effective-dart) and use `dart
format`.
- Most changes should add an entry to the changelog and may need to [rev
the pubspec package
version](https://github.com/dart-lang/sdk/blob/main/docs/External-Package-Maintenance.md#making-a-change).
- Changes to packages require [corresponding
tests](https://github.com/dart-lang/.github/blob/main/CONTRIBUTING.md#Testing).

Note that many Dart repos have a weekly cadence for reviewing PRs -
please allow for some latency before initial review feedback.
</details>