boostorg/intrusive
1
0
Fork 1
mirror of https://github.com/boostorg/intrusive.git synced 2025-08-03 14:34:44 +02:00
Code Issues Packages Projects Releases Wiki Activity

Documentation fix

Browse Source
This commit is contained in:
Ion Gaztañaga
2015-09-14 22:37:06 +02:00
parent cc9f99fc78
commit 4786f1cba9
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/intrusive.qbk
View File

@@ -1378,7 +1378,7 @@ the unordered container:
Implementing map-like intrusive containers is not a trivial task as 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 STL's `std::map` and `std::multimap` containers store copies of a `value_type` which is defined
as `std::pair<const key_type, mapped_type>`. To really mimick this interface in [*Boost.Intrusive] as `std::pair<const key_type, mapped_type>`. 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 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 `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 is limiting and also not very useful in practice. Any intrusive associative container can be used like