summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2010-11-16 22:19:06 +0000
committerChris Lattner <sabre@nondot.org>2010-11-16 22:19:06 +0000
commit221b239342d6089550ad7f49cbf49509111d3f7e (patch)
tree26a8f1a05c9087d2a39d66de329684904db4cba8 /docs
parent975176e5c6663f79ef25d86c330081f6f186af54 (diff)
downloadllvm-221b239342d6089550ad7f49cbf49509111d3f7e.tar.gz
llvm-221b239342d6089550ad7f49cbf49509111d3f7e.tar.bz2
llvm-221b239342d6089550ad7f49cbf49509111d3f7e.tar.xz
update coding standards. Partial specialization is now ok,
though possibly not a good idea. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@119398 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
-rw-r--r--docs/CodingStandards.html7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/CodingStandards.html b/docs/CodingStandards.html
index 416c29b7be..44a55a5585 100644
--- a/docs/CodingStandards.html
+++ b/docs/CodingStandards.html
@@ -397,9 +397,10 @@ portable code. If there are cases where it isn't possible to write portable
code, isolate it behind a well defined (and well documented) interface.</p>
<p>In practice, this means that you shouldn't assume much about the host
-compiler, including its support for "high tech" features like partial
-specialization of templates. If these features are used, they should only be
-an implementation detail of a library which has a simple exposed API.</p>
+compiler, and Visual Studio tends to be the lowest common denominator.
+If advanced features are used, they should only be an implementation detail of
+a library which has a simple exposed API, and preferably be buried in
+libSystem.</p>
</div>