A map is what is often called an associative array, usually implemented using a binary tree (for example). A deck is a double queue, a specific embodiment of a linked list.
This does not mean that actual container library implementations use these concepts. The custodian library will simply give you some guarantees on how you can access the container and at what (amortized) cost.
I suggest you take a look at the link that details what warranties are. Scott Meyers' book, Effective STL: 50 Concrete Ways to Improve Usage of the Standard Template Library, should talk a little about it, if I remember correctly. Also, the C ++ standard is obviously a good choice.
I really want to say: containers are really described by their properties, not the main implementation.
Jim brissom
source share