Imported Upstream version 1.72.0

[platform/upstream/boost.git] / libs / test / doc / testing_tools / boost_test_string_comparison.qbk

diff --git a/libs/test/doc/testing_tools/boost_test_string_comparison.qbk b/libs/test/doc/testing_tools/boost_test_string_comparison.qbk
index 04b1391..f49566c 100644 (file)
--- a/libs/test/doc/testing_tools/boost_test_string_comparison.qbk
+++ b/libs/test/doc/testing_tools/boost_test_string_comparison.qbk
@@ -9,9 +9,9 @@
 [section:strings Strings and C-strings comparison]
 In the general case, pointers are compared using their value. However when type of the the pointers are `char*` or `wchar_t*`,
 __BOOST_TEST__ promotes them as null terminated `char` arrays and string comparison is used instead.
-`std::string` (or any `std::basic_string`) is eligible for string comparison.
+`std::string` (or any `std::basic_string`) and `std::string_view` (or any `std::basic_string_view`) are eligible for string comparison.
 
-String comparison can be used only if the the operands to compare in __BOOST_TEST__ can both be considered as strings type.
+String comparison can be used only if the operands to compare in __BOOST_TEST__ can both be considered as strings type.
 
 [tip In this form, the comparison method and reporting can be overridden an additional argument to __BOOST_TEST__.
  See the [link boost_test.testing_tools.extended_comparison.collections collection comparison] section for more details, in particular
@@ -19,4 +19,7 @@ String comparison can be used only if the the operands to compare in __BOOST_TES
 
 [bt_example boost_test_string..BOOST_TEST string comparison..run-fail]
 
+[note `std::string_view` support added in Boost.Test [link ref_CHANGE_LOG_3_12 Boost 1.72].
+ ]
+
 [endsect]