[libcxx-commits] [libcxx] [libc++] Avoid duplicate LWGXYZ prefixes in status tables (PR #148874)

[Louis Dionne via libcxx-commits]

ldionne wrote:

CC @frederick-vs-ja  @H-G-Hristov 

I did a few things:
- I tweaked the script so it wouldn't add spurious prefixes to the status rows
- I updated several Github issues that had incorrect, outdated or missing `BEGIN-RST-NOTES/END-RST-NOTES`

The way this works is that the script parses the body of each issue for the `BEGIN-RST-NOTES` and `END-RST-NOTES` markers, and then slurps that into the notes for the status pages. This means that we should keep these annotations up-to-date in Github issues as we progress on partially-implemented papers.

For example, I added missing RST notes to https://github.com/llvm/llvm-project/issues/105180 and a few others, and I removed now-obsolete notes from other issues. As of right now, running the script produces no diff at all, which should mean that our status pages and our Github issues are 100% in sync.

If you want to try it out, I suggest you do this to avoid rate limiting by Github (this uses the `gh` command-line tool):

```
$ gh project item-list 31 --owner llvm --format json --limit 9999999 > issues.json
$ libcxx/utils/synchronize_csv_status_files.py --load-github-from issues.json
```

That way, you can run the script multiple times without extracting the project issues list, which won't work if you do it more than 2-3 times in a row (due to rate limiting).

Going forward, I would suggest that we strive to keep the Github issues up-to-date as the primary source of truth and then use the script to synchronize the status pages. But this is just a suggestion, if you folks think there's another approach that would work better, let's talk about it.

https://github.com/llvm/llvm-project/pull/148874