[docs] Clarify that there isn't much to be done other than watch build

bots when using the standard library facilities. The missing pieces here
aren't always in useful discreet chunks.

Fortunately, the missing pieces are few and far between, and we can
emulate most of them in our headers as needed.

Based on feedback from Lang and Dave.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@202548 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/docs/CodingStandards.rst b/docs/CodingStandards.rst
index 70b93a1388c4a91302fe7e7772aa007e11e1fb7c..30cc7b981e484689099bcfb123e646f6df6a6ee6 100644 (file)
--- a/docs/CodingStandards.rst
+++ b/docs/CodingStandards.rst
@@ -158,6 +158,11 @@ being aware of:
   missing. Fortunately, they are rarely needed.
 * The locale support is incomplete.
 
+Your best option if you cannot test on a Linux system is to minimize your use
+of these features, and watch the Linux build bots to find out if your usage
+triggered a bug. For example if you hit a type trait which doesn't work, we can
+then add support to LLVM's traits header to emulate it.
+
 .. _the libstdc++ manual:
   http://gcc.gnu.org/onlinedocs/gcc-4.7.3/libstdc++/manual/manual/status.html#status.iso.2011