forked from OSchip/llvm-project
update coding standards. Partial specialization is now ok,
though possibly not a good idea. llvm-svn: 119398
This commit is contained in:
parent
5b791f6e64
commit
44c2241cd4
|
|
@ -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>
|
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
|
<p>In practice, this means that you shouldn't assume much about the host
|
||||||
compiler, including its support for "high tech" features like partial
|
compiler, and Visual Studio tends to be the lowest common denominator.
|
||||||
specialization of templates. If these features are used, they should only be
|
If advanced features are used, they should only be an implementation detail of
|
||||||
an implementation detail of a library which has a simple exposed API.</p>
|
a library which has a simple exposed API, and preferably be buried in
|
||||||
|
libSystem.</p>
|
||||||
|
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue