remove LazyList<gc::HRC> specializations

[libcds.git] / cds / container / impl / lazy_kvlist.h

diff --git a/cds/container/impl/lazy_kvlist.h b/cds/container/impl/lazy_kvlist.h
index 6bd64468dd95c7c6441d5a3e9955048d93a1d4c4..4eece5c96399914da86a0758cf6879d50c9f0c1c 100644 (file)
--- a/cds/container/impl/lazy_kvlist.h
+++ b/cds/container/impl/lazy_kvlist.h
@@ -77,7 +77,6 @@ namespace cds { namespace container {
         You should include appropriate .h-file depending on GC you are using:
         - for gc::HP: \code #include <cds/container/lazy_kvlist_hp.h> \endcode
         - for gc::PTB: \code #include <cds/container/lazy_kvlist_ptb.h> \endcode
-        - for gc::HRC: \code #include <cds/container/lazy_kvlist_hrc.h> \endcode
         - for \ref cds_urcu_desc "RCU": \code #include <cds/container/lazy_kvlist_rcu.h> \endcode
         - for gc::nogc: \code #include <cds/container/lazy_kvlist_nogc.h> \endcode
     */
@@ -272,7 +271,7 @@ namespace cds { namespace container {
             The forward iterator for lazy list has some features:
             - it has no post-increment operator
             - to protect the value, the iterator contains a GC-specific guard + another guard is required locally for increment operator.
-              For some GC (gc::HP, gc::HRC), a guard is limited resource per thread, so an exception (or assertion) "no free guard"
+              For some GC (\p gc::HP), a guard is limited resource per thread, so an exception (or assertion) "no free guard"
               may be thrown if a limit of guard count per thread is exceeded.
             - The iterator cannot be moved across thread boundary since it contains GC's guard that is thread-private GC data.
             - Iterator ensures thread-safety even if you delete the item that iterator points to. However, in case of concurrent