Lines Matching +full:docs +full:- +full:clang +full:- +full:tools +full:- +full:html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
3 <html>
5 <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
6 <title>Clang - Get Involved</title>
12 <!--#include virtual="menu.html.incl"-->
16 <h1>Getting Involved with the Clang Project</h1>
18 <p>Once you have <a href="get_started.html">checked out and built</a> clang and
26 See the <a href="hacking.html">hacking</a> document for information on how
31 <p>Clang is a subproject of the <a href="https://llvm.org">LLVM Project</a>
35 <li><a href="https://discourse.llvm.org/c/clang/6">Clang Frontend Discourse forum</a> -
36 This forum is for discussions related to Clang (questions and answers, design
39 <li><a href="https://discord.gg/xS7Z362">Discord chat</a> - Real-time chat for
40 discussions related to Clang (primarily for questions and answers).</li>
45 standards-related activities happening within the Clang community. These
49 <a href="https://docs.google.com/document/d/1x5-RbOC6-jnI_NcJ9Dp4pSmGhhNe7lUevuWUIB46TeM/edit?usp=s…
53 <li><a href="https://llvm.org/docs/GettingInvolved.html#office-hours">Clang office hours</a> -
56 answered, having more in-depth design discussions, or learning about what's
59 <li><a href="https://lists.llvm.org/mailman/listinfo/cfe-commits">cfe-commits
60 </a> - Historical record of commits to Clang and contains early community patch
66 the <a href="https://discourse.llvm.org/c/clang/6">Clang Frontend Discourse forum
67 </a>. The clang forum is a very friendly place and we welcome newcomers. The
72 href="OpenProjects.html">Open Projects</a> page or look through the <a
73 href="https://github.com/llvm/llvm-project/issues/">LLVM bug tracker</a>.</p>
75 <h2 id="criteria">Contributing Extensions to Clang</h2>
77 <p>Clang is designed to support experimentation,
79 new language features and tools. At some point, the authors of these
80 extensions may propose that the extensions become a part of Clang
81 itself, to benefit the whole Clang community. However, extensions
82 (particularly language extensions) have long-term maintenance costs
83 for Clang. The benefits of the extension need to be evaluated against
84 these costs. The Clang project uses the following criteria for this
94 <li>A specific need to reside within the Clang tree: There are some extensions
96 separate tools even if they end up being hosted as part of the LLVM umbrella
107 committee and have a reasonable chance of acceptance. Clang should drive the
112 <li>A long-term support plan: increasingly large or complex extensions to
113 Clang need matching commitments to supporting them over time, including
114 improving their implementation and specification as Clang evolves. The
118 <li>A high-quality implementation: The implementation must fit well into
119 Clang's architecture, follow LLVM's coding conventions, and meet Clang's
126 extension is not broken by ongoing maintenance in Clang. The test suite
131 extension can impact other parts of the project (libc++, lldb, compiler-rt,
139 </html>