boostorg/unordered
1
0
Fork 1
mirror of https://github.com/boostorg/unordered.git synced 2025-07-30 11:27:15 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add explicit failure for noexcept_tests on gcc + fix description for Visual C++ 7.1

Browse Source
This commit is contained in:
Daniel James
2018-01-10 11:46:13 +00:00
parent f3476de893
commit a477d70f32
1 changed files with 15 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
meta/explicit-failures-markup.xml
View File

@ -17,11 +17,22 @@
<test name="compile_map_unordered_allocator"/> <test name="compile_map_unordered_allocator"/>
<toolset name="msvc-7.1"/> <toolset name="msvc-7.1"/>
<note author="Daniel James"> <note author="Daniel James">
This tests whether inserting elements creates as few copies as I think This test fail because it's using unordered's internal
is possible. If this fails it just means that the container might be allocator traits, which doesn't work on Visual C++ 7.1.
a little inefficient. It normally uses the one from Boost.Container by default.
</note> </note>
</mark-expected-failures> </mark-expected-failures>
</library>
<mark-expected-failures>
<test name="noexcept_tests"/>
<toolset name="gcc-4.3c+"/>
<note author="Daniel James">
boost::is_nothrow_move_constructible and
boost::is_nothrow_move_assignable don't seem to work on this
compiler. I'd hope that anyone wanting noexcept support would
use a more recent compiler anyway.
</note>
</mark-expected-failures>
</library>
</explicit-failures-markup> </explicit-failures-markup>