Why does std::list::reverse have O(n) complexity?(为什么 std::list::reverse 具有 O(n) 复杂度?)
问题描述
为什么C++标准库中std::list类的reverse函数有线性运行时间?我认为对于双向链表,反向函数应该是 O(1).
Why does the reverse function for the std::list class in the C++ standard library have linear runtime? I would think that for doubly-linked lists the reverse function should have been O(1).
反转双向链表应该只涉及交换头指针和尾指针.
Reversing a doubly-linked list should just involve switching the head and the tail pointers.
推荐答案
假设,reverse 可能是 O(1).(再次假设)可能有一个布尔列表成员,指示当前链接列表的方向与创建列表的原始方向相同还是相反.
Hypothetically, reverse could have been O(1). There (again hypothetically) could have been a boolean list member indicating whether the direction of the linked list is currently the same or opposite as the original one where the list was created.
不幸的是,这会降低基本上任何其他操作的性能(尽管不会改变渐近运行时).在每个操作中,需要咨询一个布尔值来考虑是否跟随链接的下一个"或上一个"指针.
Unfortunately, that would reduce the performance of basically any other operation (albeit without changing the asymptotic runtime). In each operation, a boolean would need to be consulted to consider whether to follow a "next" or "prev" pointer of a link.
由于这可能被认为是相对不常见的操作,因此标准(不规定实现,只规定复杂性)规定复杂性可以是线性的.这允许下一个"指针始终明确表示相同的方向,从而加快常见情况的操作.
Since this was presumably considered a relatively infrequent operation, the standard (which does not dictate implementations, only complexity), specified that the complexity could be linear. This allows "next" pointers to always mean the same direction unambiguously, speeding up common-case operations.
这篇关于为什么 std::list::reverse 具有 O(n) 复杂度?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:为什么 std::list::reverse 具有 O(n) 复杂度?
基础教程推荐
- 初始化列表*参数*评估顺序 2021-01-01
- 非静态 const 成员,不能使用默认赋值运算符 2022-10-09
- 为什么 typeid.name() 使用 GCC 返回奇怪的字符以及如 2022-09-16
- 为什么派生模板类不能访问基模板类的标识符? 2021-01-01
- 如果我为无符号变量分配负值会发生什么? 2022-01-01
- 通过引用传递 C++ 迭代器有什么问题? 2022-01-01
- 为什么 RegOpenKeyEx() 在 Vista 64 位上返回错误代码 2021-01-01
- GDB 显示调用堆栈上函数地址的当前编译二进制文 2022-09-05
- CString 到 char* 2021-01-01
- 我应该对 C++ 中的成员变量和函数参数使用相同的名称吗? 2021-01-01
