maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

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.

llvm-svn: 215988
This commit is contained in:
Duncan P. N. Exon Smith 2014-08-19 16:49:40 +00:00
parent 317c139f23
commit 38f556d96d
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
llvm/docs/CodingStandards.rst
View File

@ -162,6 +162,8 @@ being aware of:
* ``std::initializer_list`` (and the constructors and functions that take it as * ``std::initializer_list`` (and the constructors and functions that take it as
an argument) are not always available, so you cannot (for example) initialize an argument) are not always available, so you cannot (for example) initialize
a ``std::vector`` with a braced initializer list. 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 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 working as expected until some build bot tells you otherwise. If you're in an