You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to google-sparsehash
I wonder why "set_deleted_key()" is needed for the sparse_hash_table. After all the bitmap clearly defines which entries are occupied. Is there any special reason for this to be present?
Thanks!
philip...@gmail.com
unread,
May 29, 2016, 8:51:24 AM5/29/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
set_deleted_key only needs to be called AFAIK if you ever call "erase".
Gregory Popovitch
unread,
May 29, 2016, 2:29:03 PM5/29/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to google-sparsehash, philip...@gmail.com
Thanks for the answer, Philip, I was starting to think this group was dead. I realized that the main purpose of set_deleted_key() was to allow to erase elements without invalidating iterators. It would not be that useful if erase() was to return an iterator to the next element as specified for unordered_hash().
Gregory Popovitch
unread,
Jun 9, 2016, 6:31:43 PM6/9/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to google-sparsehash, philip...@gmail.com
Duh, answering myself here, if we just toggle the bitmap bit off when calling erase(), further lookups for keys which have the same hash as this entry will fail.