C++ 怎么样?实现了多重映射容器吗?
例如,C++ 向量是使用动态数组实现的,其中每个元素使用连续的内存空间。
我知道 C++ 多重映射是一对多关系,但内部结构是什么?
For example a C++ vector is implemented using a dynamic array where each element uses consecutive memory spaces.
I know that a C++ multimap is a one to many relationship but what is the internal structure?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
C++ 标准没有定义标准容器应该如何实现,它只给出了某些约束,就像你所说的向量一样。
多重映射具有一定的运行时复杂度(对于感兴趣的操作,O(lg n))和其他保证,并且可以实现为 红黑树。这就是它们在 GNU 标准 C++ 库中的实现方式。
The C++ standard does not define how the standard containers should be implemented, it only gives certain constraints like the one you say for vectors.
multimaps have certain runtime complexity (O(lg n) for the interesting operations) and other guarantees, and can be implemented as red-black trees. This is how they are implemented in the GNU standard C++ library.
通常,红黑树。请参见 Dobb 博士的 STL 红黑树。
Very often, a red-black tree. See e.g. STL's Red-Black Trees from Dr. Dobb's.
除了“首选”答案之外,因为 SO 不允许我发表评论:
给定一个值为 B、C、D 的键,如果每个元素都有自己的节点,则迭代器的行为会更容易实现。 Find() 定义为返回系列中的第一个结果,后续迭代将带您遍历其余元素。映射和多重映射之间事实上的区别是多重映射使用排序。在整个 value_type 上,其中映射使用 <仅针对 key_type
更正:C++11 标准明确表示新的(键、映射)对将插入到具有相同键的任何现有值的末尾。这提出了一个我没有考虑过的问题:多重映射是否可以包含两个节点,其中键和映射目标都相同。标准似乎对此没有明确的立场,但值得注意的是映射类型不需要比较运算符。如果你编写一个测试程序,你会发现多重映射可以将X映射到1,2,1。也就是说:“1”可以作为目标出现多次,并且两个实例不会合并了。对于某些算法来说这是一个缺陷。
Dobbs 博士的这篇文章讨论了底层的 rb-tree常用的实现。需要注意的要点是,重新平衡操作实际上根本不关心键,这就是为什么您可以构建一个允许重复键的 rb 树。
Addition to the "preferred" answer, because SO won't let me comment:
Given a key with values B, C, D, the behavior of iterators is a lot easier to implement if each element has it's own node. Find() is defined to return the first result in the series, and subsequent iteration takes you across the remaining elements. The de facto difference between a map and a multimap is that multimap is sorted using < over the entire value_type, where the map use < over only the key_type
Correction: the C++11 standard is explicit that new (key, mapping) pairs are inserted at the end of any existing values having the same key. This raises a question I hadn't considered: can a multimap contain two nodes in which both the key and the mapped target are the same. The standard doesn't seem to take a clear position on this, but it's noteworthy that no comparison operator is required on the mapped type. If you write a test program, you will find that a multimap can map X to 1, 2, 1. That is: "1" can appear multiple times as a target and the two instances will not be merged. For some algorithms that's a deficiency.
This article from Dr. Dobbs talks about the underlying rb-tree implementation that is commonly used. The main point to note is that the re-balance operation actually doesn't care about the keys at all, which is why you can build an rb-tree that admits duplicated keys.
多重映射就像它的简单版本一样,即 std::map,主要是使用红黑树构建的。 C++标准本身没有指定实现。但大多数情况下(我亲自查过SGI STL)都是使用红黑树。红黑树是高度平衡的树,因此对它们的获取/读取操作始终保证为 O(log(n)) 时间。但是如果您想知道键的值是如何存储的。每个
key->pair
都保存为红黑树中的单独节点(即使同一个键可能会出现多次,就像键'b'
如下)。 Key 用于查找/搜索 rb 树。一旦找到键,就会返回存储在节点中的值。输出:
最初我认为像 'b' 这样的单个键的值可能存储在 std::vector 中。
但后来我意识到这会违反 O(log(n)) 的保证获取时间。此外,打印出值的地址可以确认具有公共键的值不是连续的。
它们的键是使用运算符<插入的,因此具有相同键的值按照插入的顺序存储。
所以如果我们先插入
(键 = 'b',值 = 20)
进而
(键 = 'b',值 = 10)
插入是使用operator< 完成的。 ,由于第二个“b”不小于第一个插入的“b”,因此它被插入“二叉树的右分支”。
我使用的编译器是gcc-5.1(C++14)。
The multimap just like it's simpler version i.e the std::map, is mostly built using red black trees. C++ standard itself does not specify the implementation. But in most of the cases ( I personally checked SGI STL) red black trees are used. Red Black trees are height balanced trees and hence fetch / read operation on them is always guaranteed to be O(log(n)) time. But if you are wondering on how values of the key are stored. each
key->pair
is saved as a separate node in the red black tree ( Even though the same key might appear multiple times just like in the case of key'b'
below). Key is used to lookup/ search the rb-tree. Once the key is found, it's value stored in the node is returned.Output :
Initially I thought the values of a single key like 'b' might be stored in a std::vector .
But later I realized that would violate the guaranteed fetch time of O(log(n)). Moreover, printing out the addresses of the values confirms that values with a common key are not contiguous.
They keys are inserted using operator<, so values with the same keys are stored in the order in which they are inserted.
So if we insert first
(key = 'b', value = 20)
and then
(key = 'b', value = 10)
The insertion is done using operator< , since the second 'b' is NOT lesser than the first inserted 'b', it is inserted in the 'right branch of a binary tree'.
The compiler I have used is gcc-5.1 ( C++14).