<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">There's no (direct) overlap with the latter proposal (my own), although we should think about how to integrate them.  My proposal leaves separate the challenge of writing matchers, so this would be a nice addition for users.  I suspect there's significant overlap with Stephen's work, although I think they're targeting a somewhat different interface with the tool.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Shyan -- do you have an overview of your tool that you could share with us?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 21, 2019 at 8:29 AM Jonas Toth via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF">
    <p>See the thread "[cfe-dev] Separating clang-tools-extra from clang
      in LLVM_ENABLE_PROJECTS" as well.</p>
    <p>What tool is it and how does it help? Did you notice the
      "[cfe-dev] [RFC] Easier source-to-source transformations with
      clang tooling" thread here proposing a better
      matching&transforming API?<br>
    </p>
    <div class="gmail-m_7923489784225777559moz-cite-prefix">Am 21.02.19 um 02:14 schrieb Shyan
      Akmal via cfe-dev:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="ltr">Hello,
        <div><br>
        </div>
        <div>I'm working with a few other developers on creating a clang
          tool. This tool is meant to help out with the development of
          clang-tidy checks (specifically to help with writing
          matchers). </div>
        <div><br>
        </div>
        <div>Currently, the tool is contained as a single folder within
          the <i>clang/tools/extra</i> directory. However, we realized
          that several other tools seem to be located outside of clang
          extra, in <i>clang/lib</i> or <i>clang/lib/tooling</i>.</div>
        <div><br>
        </div>
        <div>Given this, we had a quick question: should we move our
          tool to <i>clang/lib</i>, keep it in <i>clang/tools/extra</i>,
          or place it somewhere else? Or, does the placement not matter
          that much? </div>
        <div><br>
        </div>
        <div>Sincerely,</div>
        <div>Shyan</div>
      </div>
      <br>
      <fieldset class="gmail-m_7923489784225777559mimeAttachmentHeader"></fieldset>
      <pre class="gmail-m_7923489784225777559moz-quote-pre">_______________________________________________
cfe-dev mailing list
<a class="gmail-m_7923489784225777559moz-txt-link-abbreviated" href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>
<a class="gmail-m_7923489784225777559moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a>
</pre>
    </blockquote>
  </div>

_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
</blockquote></div>