From: Duncan P. N. Exon Smith Date: Tue, 19 Aug 2014 16:49:40 +0000 (+0000) Subject: CodingStandards: Document std::equal misbehaviour X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2788345a9b58d97f0bd1d1c22381aeec125d73aa;p=llvm CodingStandards: Document std::equal misbehaviour I should have included this as part of r215986, which worked around this corner by changing ArrayRef::equals() not to use std::equal. Alas. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@215988 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/CodingStandards.rst b/docs/CodingStandards.rst index 3cfa1f66ab4..7aa28f346c5 100644 --- a/docs/CodingStandards.rst +++ b/docs/CodingStandards.rst @@ -162,6 +162,8 @@ being aware of: * ``std::initializer_list`` (and the constructors and functions that take it as an argument) are not always available, so you cannot (for example) initialize a ``std::vector`` with a braced initializer list. +* ``std::equal()`` (and other algorithms) incorrectly assert in MSVC when given + ``nullptr`` as an iterator. Other than these areas you should assume the standard library is available and working as expected until some build bot tells you otherwise. If you're in an