aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test
diff options
context:
space:
mode:
authorVlad Serebrennikov <serebrennikov.vladislav@gmail.com>2024-04-29 15:03:13 +0400
committerGitHub <noreply@github.com>2024-04-29 15:03:13 +0400
commit37f2928ce382603fdadd7bae87fa245ac65b7d4f (patch)
tree846522f2c31e2c01fc1dbc1ee4306a7738791acb /lldb/packages/Python/lldbsuite/test
parentf2452d4b689469b6da63d9e8ffa96eaf4b39ac5d (diff)
downloadllvm-37f2928ce382603fdadd7bae87fa245ac65b7d4f.zip
llvm-37f2928ce382603fdadd7bae87fa245ac65b7d4f.tar.gz
llvm-37f2928ce382603fdadd7bae87fa245ac65b7d4f.tar.bz2
[clang] Use `cwg_index.html` from GitHub for DR status page (#90352)
Currently we're using official publication of CWG issue list available at https://www.open-std.org/jtc1/sc22/wg21/docs/cwg_index.html. Unfortunately, it's not updated as frequently as we sometimes need. For instance, recently there was a confusion during review of CWG2149 test (https://github.com/llvm/llvm-project/pull/90079#discussion_r1580174003). This patch changes our `make_cxx_dr_status` script to use issue list from CWG GitHub repository. I confirmed with CWG chair that this is the most up-to-date source of information on CWG issues. Changing the source of issue list uncovered previously unhandled "tentatively ready" status of an issue. This status is considered unresolved by the script (like `open`, `drafting`, and `review`), as the resolution might change during face-to-face CWG meeting. I also noticed that CWG decided to handle 2561 differently from what we're doing, so this DR is now considered not available in Clang, despite being declared as available since 18. CC @cor3ntin. This patch also brings new issues into our DR list, so if someone was waiting for a newly-filed issue to appear on our status page, it should appear with this PR.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
0 files changed, 0 insertions, 0 deletions