- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
我可以/应该继承STL迭代器来实现我自己的迭代器类吗?如果不是,为什么不呢?
最佳答案
许多人认为,与常规类型别名相比,类 std::iterator
并没有提供太多功能,甚至通过不显式提供名称并依赖于模板参数的顺序来稍微混淆它们反而。它在 C++17 中已被弃用,并且可能会在几年内消失。
这意味着您不应再使用std::iterator
。如果您对整个故事感兴趣,可以阅读下面的整篇文章(有一点冗余,因为它是在弃用提案之前开始的)。
如果您对历史不感兴趣,可以忽略下面的所有内容。以下片段甚至多次自相矛盾。
从今天(C++11/C++14)开始,该标准似乎暗示从 std::iterator
继承来实现自定义迭代器不再是一个好主意。这里有一个简单的解释,来自N3931 :
Although the Standard has made this mistake almost a dozen times, I recommend not depicting
directory_iterator
andrecursive_directory_iterator
as deriving fromstd::iterator
, since that's a binding requirement on implementations. Instead they should be depicted as having the appropriate typedefs, and leave it up to implementers to decide how to provide them. (The difference is observable to users withis_base_of
, not that they should be asking that question.)[2014-02-08 Daniel comments and provides wording]
This issue is basically similar to the kind of solution that had been used to remove the requirement to derive from
unary_function
and friends as described by N3198 and I'm strongly in favour to follow that spirit here as well. I'd like to add that basically all "newer" iterator types (such as theregex
related iterator) don't derive fromstd::iterator
either.
论文引用了N3198它本身声明它遵循 N3145 中讨论的弃用。 。弃用仅提供 typedef
的类的原因如下:
Our experience with concepts gives us confidence that it is rarely necessary to depend on specific base class-derived class relations, if availability of types and functions is sufficient. The new language tools allow us even in the absence of language-supported concepts to deduce the existence of typenames in class types, which would introduce a much weaker coupling among them. Another advantage of replacing inheritance by associated types is the fact, that this will reduce the number of cases, where ambiguities arise: This can easily happen, if a type would inherit both from
unary_function
andbinary_function
(This makes sense, if a functor is both an unary and a binary function object).
tl;dr:仅提供 typedef
的类现在被认为是无用的。此外,它们会在不需要时增加耦合,更加冗长,并且在某些极端情况下可能会产生不必要的副作用(请参阅前面的引用)。
更新: issue 2438 from N4245似乎实际上与我之前的断言相矛盾:
For LWG convenience, nine STL iterators are depicted as deriving from
std::iterator
to get theiriterator_category
/etc. typedefs. Unfortunately (and unintentionally), this also mandates the inheritance, which is observable (not just throughis_base_of
, but also overload resolution). This is unfortunate because it confuses users, who can be misled into thinking that their own iterators must derive fromstd::iterator
, or that overloading functions to takestd::iterator
is somehow meaningful. This is also unintentional because the STL's most important iterators, the container iterators, aren't required to derive fromstd::iterator
. (Some are even allowed to be raw pointers.) Finally, this unnecessarily constrains implementers, who may not want to derive fromstd::iterator
. (For example, to simplify debugger views.)
总而言之,我错了,@aschepler 是对的:它可以可以使用,但它肯定不是必需的 - 也不劝阻它。整个“让我们删除 std::iterator
” 的存在是为了让标准不限制标准库实现者。
第三轮: P0174R0建议弃用 std::iterator
以便将来可能删除。该提案已经很好地解释了为什么应该弃用它,所以我们开始:
The long sequence of void arguments is much less clear to the reader than simply providing the expected typedefs in the class definition itself, which is the approach taken by the current working draft, following the pattern set in C++14 where we deprecated the derivation throughout the library of functors from unary_function and binary_function.
In addition to the reduced clarity, the iterator template also lays a trap for the unwary, as in typical usage it will be a dependent base class, which means it will not be looking into during name lookup from within the class or its member functions. This leads to surprised users trying to understand why the following simple usage does not work:
#include <iterator>
template <typename T>
struct MyIterator : std::iterator<std::random_access_iterator_tag, T> {
value_type data; // Error: value_type is not found by name lookup
// ... implementations details elided ...
};The reason of clarity alone was sufficient to persuade the LWG to update the standard library specification to no longer mandate the standard iterator adapators as deriving from std::iterator, so there is no further use of this template within the standard itself. Therefore, it looks like a strong candidate for deprecation.
这变得有点累,而且似乎并不是每个人都同意,所以我会让你得出自己的结论。如果委员会最终决定应弃用 std::iterator,那么它将非常清楚地表明您不应再使用它。请注意 follow-up paper突出显示对删除 std::iterator
的大力支持:
Update from Jacksonville, 2016:
Poll: Deprecate
iterator
for C++17??
SF F N A SA
6 10 1 0 0
在上述投票结果中,SF、F、N、A 和 SA 代表强烈支持、赞成、中立、反对和强烈反对>.
Update from Oulu, 2016:
Poll: Still want to deprecate
std::iterator?
SF F N A SA
3 6 3 2 0
P0619R1建议尽快从 C++20 开始删除 std::iterator
,并且还建议增强 std::iterator_traits
以便它可以自动推导类型 difference_type
、pointer
和 reference
与 std::iterator
在未明确提供时的方式相同。
关于c++ - 我可以/应该从 STL 迭代器继承吗?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/6471019/
我正在尝试在Elasticsearch中返回的值中考虑地理位置的接近性。我希望近距离比某些字段(例如legal_name)重要,但比其他字段重要。 从文档看来,当前的方法是使用distance_fea
我是Elasticsearch的初学者,今天在进行“多与或”查询时遇到问题。 我有一个SQL查询,需要在Elastic中进行转换: WHERE host_id = 999 AND psh_pid =
智能指针应该/可以在函数中通过引用传递吗? 即: void foo(const std::weak_ptr& x) 最佳答案 当然你可以通过const&传递一个智能指针。 这样做也是有原因的: 如果接
我想执行与以下MYSQL查询等效的查询 SELECT http_user, http_req_method, dst dst_port count(*) as total FROM my_table
我用这两个查询进行测试 用must查询 { "size": 200, "from": 0, "query": { "bool": { "must": [ { "mat
我仍在研究 Pro Android 2 的简短服务示例(第 304 页)同样,服务示例由两个类组成:如下所示的 BackgroundService.java 和如下所示的 MainActivity.j
给定标记 like this : header really_wide_table..........................................
根据 shouldJS 上的文档网站我应该能够做到这一点: ''.should.be.empty(); ChaiJS网站没有使用 should 语法的示例,但它列出了 expect 并且上面的示例似乎
我在 Stack Overflow 上读到一些 C 函数是“过时的”或“应该避免”。你能给我一些这种功能的例子以及原因吗? 这些功能有哪些替代方案? 我们可以安全地使用它们 - 有什么好的做法吗? 最
在 C++11 中,可变参数模板允许使用任意数量的参数和省略号运算符 ... 调用函数。允许该可变参数函数对每个参数做一些事情,即使每个参数的事情不是一样的: template void dummy(
我在我从事的项目之一上将Shoulda与Test::Unit结合使用。我遇到的问题是我最近更改了此设置: class MyModel :update end 以前,我的(通过)测试看起来像这样: c
我该如何做 or使用 chai.should 进行测试? 例如就像是 total.should.equal(4).or.equal(5) 或者 total.should.equal.any(4,5)
如果您要将存储库 B 中的更改 merge 到存储库 A 中,是否应该 merge .hgtags 中的更改? 存储库 B 可能具有 A 中没有的标签 1.01、1.02、1.03。为什么要将这些 m
我正在尝试执行X AND(y OR z)的查询 我需要获得该代理为上市代理或卖方的所有已售属性(property)。 我只用 bool(boolean) 值就可以得到9324个结果。当我添加 bool
我要离开 this教程,尝试使用 Mocha、Supertest 和 Should.js 进行测试。 我有以下基本测试来通过 PUT 创建用户接受 header 中数据的端点。 describe('U
我正在尝试为 Web 应用程序编写一些 UI 测试,但有一些复杂的问题希望您能帮助我解决。 首先,该应用程序有两种模式。其中一种模式是“训练”,另一种是“现场”。在实时模式下,数据直接从我们的数据库中
我有一个规范: require 'spec_helper' # hmm... I need to include it here because if I include it inside desc
我正在尝试用这个测试我在 Rails 中的更新操作: context "on PUT to :update" do setup do @countdown = Factory(:count
我还没有找到合适的答案: onclick="..." 中是否应该转义 &(& 符号)? (或者就此而言,在每个 HTML 属性中?) 我已经尝试在 jsFiddle 和 W3C 的验证器上运行转义和非
import java.applet.*; import java.awt.*; import java.awt.event.*; public class Main extends Applet i
我是一名优秀的程序员,十分优秀!