From 4786f1cba9fb6227863be2a61960e2be14a81825 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ion=20Gazta=C3=B1aga?= Date: Mon, 14 Sep 2015 22:37:06 +0200 Subject: [PATCH] Documentation fix --- doc/intrusive.qbk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/intrusive.qbk b/doc/intrusive.qbk index 65affa3..e7e7693 100644 --- a/doc/intrusive.qbk +++ b/doc/intrusive.qbk @@ -1378,7 +1378,7 @@ the unordered container: Implementing map-like intrusive containers is not a trivial task as STL's `std::map` and `std::multimap` containers store copies of a `value_type` which is defined -as `std::pair`. To really mimick this interface in [*Boost.Intrusive] +as `std::pair`. In order to reproduce this interface in [*Boost.Intrusive] it shall require that objects stored in the intrusive containers contain that `std::pair` member with `pair.first` hardcoded as the key part and `pair.second` hardcoded as the `mapped_type`, which is limiting and also not very useful in practice. Any intrusive associative container can be used like