<table border="1" cellspacing="0" cellpadding="8">
    <tr>
        <th>Issue</th>
        <td>
            <a href=https://github.com/llvm/llvm-project/issues/79219>79219</a>
        </td>
    </tr>

    <tr>
        <th>Summary</th>
        <td>
            [libc++] Use Github tools to track our Standards conformance
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            libc++
      </td>
    </tr>

    <tr>
      <th>Assignees</th>
      <td>
            ldionne
      </td>
    </tr>

    <tr>
      <th>Reporter</th>
      <td>
          ldionne
      </td>
    </tr>
</table>

<pre>
    This issue is a reboot of https://github.com/llvm/llvm-project/issues/52642.

Libc++ currently tracks its conformance status in CSV files that we update manually. Unfortunately, this is not very well integrated with the rest of our development workflows, which revolve around Github. This issue tracks the investigation to move from CSV files to Github issues (or milestones, or projects, or something else) for conformance tracking in libc++. This would provide the following benefits:
- Better integration with the rest of our workflows (e.g. issues closed automatically when landing a PR)
- Better ability to filter things in the UI via tags (e.g. show me all unassigned LWG issues that were included in C++20)

However, when we discussed it in [the Libc++ monthly meeting](https://docs.google.com/document/d/1yC-3bE6pefVizUhfiUs1Shv11EzuL0KOklGSLqto6dk/edit?usp=sharing) on January 23rd 2024, we identified the following two requirements for this migration to be viable:
1. We need the ability to generate a status page for our documentation so that users can still see the status of libc++ on llvm.org. Users shouldn't have to go to Github and do some research to find this status.
2. We need to ensure that it's easy to find the status of a LWG issue or paper. Today we can basically just `grep` the codebase and we'll find the status via the CSV file. We should have an easy workflow accessible, for example by using the `gh` command-line tool.
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJycVU1z2zYQ_TXQZccaEpQs6aBDbEfph2faqePkDBJLEjGIVYCFWOXXdwBSipL21Att08Tue2_fw6oQTOcQ92L9IKS02pBzKKQU66eFityT388vFzXp8_5jbwKYECKCCaDAY03EQC30zMcgqndCHoQ8dIb7WC8bGoQ8WHu6_Lg7evqCDQt5yFWCkIe1vF_JpSieRPFuej6buhHyQcgHaKL36Niegb1q3gIYDtCQa8kPyjUIgRXHAMbB48snaI3FANwrhhEhHrVihEG5qKw9L-E1nePoFKM9C_kIPPEBRwwn9GcY0VowjrHzilHDaLgH7hE8hsyTogeNJ7R0HNAxjOTfWktjSOXG3jQ9eDyRPSEoT9Fp-DBpATfazVxSXeNOGNh0ig05YIKBTgitp-GWEM1VpvMBhNyShyH9k8lhbk4eZnUvfwYakHvjOkAbUMgdtOR_UC8DSR8YB_aq-ox1pGh1qnkyGjPYlqylMX1fo8PWcJ54ntkdPCAz-qt4ic5_qndVLLHAZbe8kGosBdSgItOg2DRpZjD26MAqp1NXBX_-JeTup46qNtbwOanUGpveZNLZFKn5669wMgpYdd9bhp5GGBCUtRDdnAMNz58_XNDMJvJpRI2NGnU22aSQLK4wpucvNOIJ_WQCdMl92oQmhsTIcDoq1g8JzY25B3Lc2zMMiGxcJ9ZPQm5_DJKmJiw7os7inCZNTUzOS78KeSjPj3dV_f7-iO0n8-21b81rKF_6U1m-_xafi9__eLMfXp6_Mt3rNyEPqA2L6hDDUVRPoVc-9ZU7IAe_pZj4M8jKa5CFXGUyCEajY9Ma1D95gEcCj1-j8ZgAheyunKjBXBzABDUm-WuLV6-US_iM4HCueDO_Dh2m4IG6BPuoOsyFc_Bm7lPtQNOQYkAfoFEOAhtrIeDk1rkCtTfWTkTTRbQk3y3hNZ8MfTK6E3LD0KsTZiB0EzrlNGjKcUpORuWbfnKb0xPhqdV8ickbegToQvQ4ITUs5CYAqnC-OX-LVH23YA60OqJfwkfSKt1NmWStwpyNLzEwiPui83gU90Uu1ZDGWgXMoEcUcmPtvxrlOPR4vWEy4EmGSQHlJpCXrIJqGgzBpCnKxzwP_FsNR4tQnyGGbIceM5g-QWloGJTTd9a4pCfZ5ULvK72rdmqB-3JT3Ber7aoqFv1-peptuSvX7abZ7Ypdg7LYFFW1LdV2XcpSLcw-ubEoZSWlLKpiWbXbatvU2xrVrt0WtVgVOChjl5fJLrKA-81OlruFVTXacFlxVyfMW87v816qYxfEqrAmcPhehg3bvBxvjq2fkm0u1kjU8v2cb9Js0hdWTiuvf9hTi-jt_v_vyMzknwAAAP__cD6feA">