id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
9949,clear header node hooks upon intrusive container destruction,Matei David <matei@…>,Ion Gaztañaga,"In intrusive containers, the `safe_link` and `auto_unlink` hook types cause boost to reset the hooks to their default constructed state (usually `NULL`) upon removing an element from a container. That suggests a user could double check that nodes are indeed removed from all containers upon destruction, by checking that the hooks are set to `NULL`. Unfortunately, the check fails because, unlike all other regular nodes, the hooks of the container //header// nodes are not reset upon destruction of the container.

I will create a pull request which rectifies this in `list`, `slist`, and `bstree`. I will drop it on top of the develop branch, which has the recent fix to bug #9940.

I believe the change should have no negative impact.",Feature Requests,closed,To Be Determined,intrusive,Boost 1.55.0,Problem,fixed,intrusive header hooks,