为什么 C++11 或 C++14 中没有位置迭代器?

2022-01-10 00:00:00 iterator c++ c++11 stl c++14

C++98 有 front_inserterback_inserterinserter,但似乎没有这些的任何 emplacement 版本C++11 或草案 C++14.我们不能拥有 front_emplacerback_emplaceremplacer 是否有任何技术原因?

C++98 has front_inserter, back_inserter, and inserter, but there don't seem to be any emplacement versions of these in C++11 or draft C++14. Is there any technical reason we couldn't have front_emplacer, back_emplacer, and emplacer?

推荐答案

我们不能有front_emplacer、back_emplacer和emplacer有什么技术原因吗?

Is there any technical reason we couldn't have front_emplacer, back_emplacer, and emplacer?

不,没有技术原因.作为证明,这里是 back_emplacer 的完整实现,并带有您的用例 1 的演示......

No, there is no technical reason. As proof, here is a complete implementation of back_emplacer with a demo of your Use Case 1...

#include <iterator>
#include <vector>
#include <iostream>

template<class Container>
class back_emplace_iterator : public std::iterator< std::output_iterator_tag,
                                                   void, void, void, void >
{
protected:
    Container* container;
public:
    typedef Container container_type;

    explicit back_emplace_iterator(Container& x) : container(&x) {}

    template<class T>
    back_emplace_iterator<Container>&
    operator=(T&& t)
    {
        container->emplace_back(std::forward<T>(t));
        return *this;
    }

    back_emplace_iterator& operator*() { return *this; }
    back_emplace_iterator& operator++() { return *this; }
    back_emplace_iterator& operator++(int) { return *this; }
};

template< class Container >
inline back_emplace_iterator<Container>
back_emplacer( Container& c )
{
    return back_emplace_iterator<Container>(c);
}

struct Demo
{
    int i;
    Demo(int i) : i(i) {}
};

int main()
{
    std::vector<int> x = {1,2,3,4,5};

    std::vector<Demo> y;

    std::copy(x.begin(), x.end(), back_emplacer(y));

    for (auto d : y)
        std::cout << d.i << std::endl;
}

可能的已知问题:operator= 的通用引用是否隐藏了隐式生成的复制/移动 operator=?如果是这样,则需要以优于重载决议中的通用引用的方式明确定义这些.

Possible Known Issue: Does the universal reference of operator= hide an implicitly generated copy/move operator=? If so these need to be explicitly defined in a way that beats the universal reference in overload resolution.

相关文章