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

diff --git a/docs/CodingStandards.html b/docs/CodingStandards.html
index 416c29b7bedd35db687766745640b37bd95c393b..44a55a55857548133d99fa24c2cd8346a65dda72 100644 (file)
--- 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>