From 6e5f25c98077d24d1e1f5ca093f927d26c5774af Mon Sep 17 00:00:00 2001 From: khizmax Date: Sun, 26 Mar 2017 11:20:35 +0300 Subject: [PATCH] Docfix --- cds/intrusive/details/base.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cds/intrusive/details/base.h b/cds/intrusive/details/base.h index 3dea55d1..51189679 100644 --- a/cds/intrusive/details/base.h +++ b/cds/intrusive/details/base.h @@ -40,12 +40,12 @@ namespace cds { /// Intrusive containers /** @ingroup cds_intrusive_containers - The namespace cds::intrusive contains intrusive lock-free containers. + The namespace \p cds::intrusive contains intrusive lock-free containers. The idea comes from \p boost::intrusive library, see http://boost.org/doc/ as a good introduction to intrusive approach. The intrusive containers of libcds library is developed as close to \p boost::intrusive In terms of lock-free approach, the main advantage of intrusive containers is - that no memory allocation is performed to maintain container items. + that no memory allocation is performed to maintain container elements. However, additional requirements are imposed for types and values that can be stored in intrusive container. See the container documentation for details. -- 2.34.1