Lines Matching +full:feature +full:- +full:rich
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
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"-->
36 <li><a href="http://lists.llvm.org/mailman/listinfo/cfe-commits">cfe-commits
37 </a> - This list is for patch submission/discussion.</li>
39 <li><a href="http://lists.llvm.org/mailman/listinfo/cfe-dev">cfe-dev</a> -
48 href="http://lists.llvm.org/mailman/listinfo/llvm-dev">llvm-dev</a> and <a
49 href="http://lists.llvm.org/mailman/listinfo/llvm-commits">llvm-commits</a>
54 href="http://lists.llvm.org/mailman/listinfo/cfe-dev">cfe-dev mailing
56 newcomers. In addition to the cfe-dev list, a significant amount of design
58 href="http://lists.llvm.org/mailman/listinfo/cfe-commits">cfe-commits mailing
76 itself, to benefit the whole Clang community. But not every idea--not
77 even every great idea--should become part of Clang. Extensions
78 (particularly language extensions) pose a long-term maintenance burden
84 … would adopt such a feature if it were available, and any "trickle-down" effects that come from, e…
88 …feature as well as interpret the meaning of specific examples. The specification should be detaile…
92 …<li>A long-term support plan: Contributing a non-trivial extension to Clang implies a commitment t…
94 …-quality implementation: The implementation must fit well into Clang's architecture, follow LLVM's…
96 …her compiler vendor could conceivably validate their implementation of the feature against it.</li>