admin管理员组

文章数量:1435859

I have a class with a mutex in it:

Class StoreNumbers{
  StoreNumbers();
  AddNumber(size_t number){
    const std::lock_guard<std::mutex> lock(lock_);
    numbers_.push_back(number);
  }

  private:
  std::mutex lock_;
  std::vector<size_t> numbers_;

};

The purpose of the class is to be able to store numbers while used in a multithreaded context. There is certainly better ways to do that but that illustrates my question.

Now I want to have various objects of these classes, in order to store different types of numbers. I also want each of these types to have a different mutex, since they are unrelated.

If I write:

std::vector<StoreNumbers> vec;
vec.push_back(StoreNumber());

I get the compiler error: no matching function for call to 'construct_at', which I understand since the mutex is non copyable.

If instead I use:

std::unique_ptr<std::mutex> lock_=std::make_unique<std::mutex>();

for the lock and dereference it for the lock_guard, I do not get the error anymore. I do not understand why. Thanks for the help!

本文标签：

版权声明：本文标题：mutex - Why does the unique_pointer solve the &quot;no matching function for call to &#39;construct_at&#39;&quot 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1745672145a2669635.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。