tags:

views:

451

answers:

6

When should I choose one over the other. Are there any pointers that you would recommend for using the right STL containers.

+1  A: 

There is a discussion related to this here:

http://stackoverflow.com/questions/222658/multiset-map-and-hash-map-complexity

Edit:

Adam Rosenfield's answer on that question lays out the big-O for each.

itsmatt
A: 

A hash_set would be implemented by a hash table, which has mostly O(1) operations, whereas a set is implemented by a tree of some sort (AVL, red black, etc.) which have O(log n) operations, but are in sorted order.

Edit: I had written that trees are O(n). That's completely wrong.

Alex Gaynor
O(log n) for trees
Andrey
red-black trees are O(n)?
anon
Oh jesus, I can't believe I wrote O(n). That's probably the dumbest thing I've done all day.
Alex Gaynor
+3  A: 

hash_set is an extension that is not part of the C++ standard. Lookups should be O(1) rather than O(log n) for set, so it will be faster in most circumstances.

Another difference will be seen when you iterate through the containers. set will deliver the contents in sorted order, while hash_set will be essentially random (Thanks Lou Franco).

Mark Ransom
Also, set is ordered.
Lou Franco
+1  A: 

stl::set is implemented as a binary search tree. hashset is implemented as a hash table.

The main issue here is that many people use stl::set thinking it is a hash table with look up of O(1), which it isn't, and doesn't have. It really has O(log(n)) for look ups. Other then that read about binary trees vs hash tables to get a better idea of the datastructures.

windfinder
Why did this get downvoted? -- a red-black tree is a kind of binary search tree, and the spec doesn't say it has to be red-black -- it just set big-O parameters for the operations.
Lou Franco
+1  A: 

Another thing to keep in mind is that with hash_set you have to provide the hash function, whereas a set only requires a comparison function ('<') which is easier to define (and predefined for native types).

ronys
There are hash functions for native types too.
Lou Franco
A: 

I don't think anyone has answered the other part of the question yet.

The reason to use hash_set or unordered_set is the usually O(1) lookup time. I say usually because every so often, depending on implementation, a hash may have to be copied to a larger hash array, or a hash bucket may end up containing thousands of entries.

The reason to use a set is if you often need the largest or smallest member of a set. A hash has no order so there is no quick way to find the smallest item. A tree has order, so largest or smallest is very quick. O(log n) for a simple tree, O(1) if it holds pointers to the ends.

Zan Lynx