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

    <tr>
        <th>Summary</th>
        <td>
            [libc][test] the LibcTest API should be a subset of the gtest API
        </td>
    </tr>

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

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

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

<pre>
    Problems brought up in the May 9 libc meeting, [meeting notes here](https://discourse.llvm.org/t/monthly-llvm-libc-meeting/74259/16):

- [ ] in gtest all the assert macros are allowed to be within sub functions, whereas our current framework doesn’t - Roland is working on this
- [ ] The custom matchers also don’t work as gtest matchers - I will work on this 
- [ ] If we [are gtest compatible], we should have an upstream gtest buildbot

@frobtech 
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJxcktFuozoQhp_G3IwSgROHcMFF2xykSOdI1VFfwDZD7F2DI8-4Ud9-ZZLtdnsDMp75Z_6fTxP5y4LYC_Us1KnSmV1M_RD0MvrFVyaOH_1riibgTGBSzBfHkK_gF2CH8J_-gA6CNxZmRPbLRcgXEOr5cYIlMhI4TCjUScijY76S2D0JOQg5jJ5szIlwG8L7vI3pIuTAQg5zXNiFj035vCnym0_5od1L1Qk5NAchuyJVn0T9eG7KbBDqVBa8MBKDDmFdVRNhYpi1TZFAJyw38YYjcASDcPPs_AKUDUx5sezjQsXMrSyvCWJOYHNKuDBMSc94i-knjBFpEf9IcaxF1zFs4P9YwgNPUApKBrFk5en7hm8OwWbiOMOs2TpMBDpQhDF-VVzHaHq4-azcwBluPoT7_WMEfJ9xnuCG5VT83hVsnK-avQn3P_JSCsjFHEZw-h1BL5CvxAn1_Ogw2YfRRP4atNjXU4qG0Tqoxn43drtOV9g3baNkq9qdrFx_UFNT43Eyh0kdWnk8YGPaUbZmPympO1v5XtZyX6u6a1p5VHIrlZmaboetUbbdKSP2Nc7ah08-Kk-Use-aw66ugjYYaGVXykKJkLJQnPqVG5MvJPZ18MT0R4A9h5X3tUGdhHouLktaBZN_vbFvxfXT6_l3LgZBFzAIGeK0lt2TeXo9VzmF_m-qL55dNlsbZyGHMvfx2lxT_IG28L26ICGH1civAAAA__8ZdiMK">