- 
    Enhancement 
- 
    Resolution: Won't Fix
- 
     P4 P4
- 
    21
- 
        generic
- 
        generic
                    Apply the same idea of JDK-8300184 to unlink(). 
Because ResourceHashtableBase doesn't support copy constructor and copy assignment, client of it has to purge all elements first. We would like provide a specialized version called 'unlink_all()'. We don't need to update each node's _next in this case. We could nullify each bucket. We could also use unlink_all() in destructor.
            
Because ResourceHashtableBase doesn't support copy constructor and copy assignment, client of it has to purge all elements first. We would like provide a specialized version called 'unlink_all()'. We don't need to update each node's _next in this case. We could nullify each bucket. We could also use unlink_all() in destructor.
- relates to
- 
                    JDK-8300184 Optimize ResourceHashtableBase::iterate_all using _number_of_entries -           
- Resolved
 
-         
- 
                    JDK-8301296 Unify ResourceHashtable APIs for removing entries -           
- Closed
 
-         
- links to
- 
                     Review
        openjdk/jdk/12213 Review
        openjdk/jdk/12213
