从零开始写STL - 智能指针
从零开始写STL - 智能指针
- 智能指针的分类及其特点:
scoped_ptr:初始化获得资源控制权,在作用域结束释放资源
shared_ptr: 引用计数来控制共享资源,最后一个资源的引用被释放的时候会析构
unique_ptr: 只能有一个持有资源引用的对象
weak_ptr:eak_ptr也维护了一个引用计数,跟shared_ptr维护的引用计数或互不干扰,或相互协同。weak_ptr的指针会在weak_ptr维护的引用计数上加一,而shared_ptr会在shared_ptr维护的引用计数上加一,这样在循环引用时,就会因为对不同引用的判断的不同,使最终决定是否释放空间的结果也不相同。
定制化删除器
在某些特定情况下,我们需要定制化的对象清理行为
比如在服务器端保持一个 Session的列表,由于要保证Session的动态销毁,应该使用unordered_map<weak_ptr_to_session > 来高效检索对象(如果使用shared_ptr 会导致对象生存期过长(直到服务器端销毁map)),此时我们在shared_ptr_to_session里面应该定制化这样的清理操作:在清理自身管理的内存对象的同时,应该对哈希表中删除对应的weak_ptr(否则哈希表中只添加不删除也是一种内存泄露)。
如何实现
- 默认模板类型 + std::bind函数
template<typename T>
class Deleter {
public:
typedef std::function<void(T*)> DeleteFunc;
//默认删除
Deleter(): func(std::bind(&Deleter::defaultfunc,this, std::placeholders::_1)){}
//定制化
Deleter(DeleteFunc df) :func(df) {}
void operator()(T* p) const {
func(p);
};
private:
void defaultfunc(T* ptr) {
ptr->~T();
}
DeleteFunc func;
};
unique_ptr
最简单的智能指针类型,注意在所有权转移时将对应的原对象析构即可。
//默认使用delete 来销毁类型
template<typename T, typename Deleter = ministl::Deleter<T>>
class unique_ptr {
public:
typedef T* pointer;
unique_ptr() :data(nullptr), delfunc() {}
unique_ptr(const unique_ptr<T>&) = delete;
unique_ptr(unique_ptr<T>&& rhs) :delfunc(rhs.delfunc), data(rhs.data) {
rhs.data = nullptr;
}
unique_ptr<T>& operator=(const unique_ptr<T>& rhs) = delete;
~unique_ptr() {
delfunc(data);
}
void reset() {
delfunc(data);
data = nullptr;
}
void reset(T* _data) {
delfunc(data);
data = _data;
}
pointer release() noexcept {
pointer ret = data;
data = nullptr;
return ret;
}
pointer get() const noexcept {
return data;
}
T& operator * () const noexcept{
return *data;
}
T* operator ->() const noexcept{
return &*this;
}
private:
Deleter delfunc;
T* data;
};
shared_ptr
实现的几个问题:
- 引用计数如何保存?
每个shared_ptr 维护一个指针,指向共享引用计数节点,节点中保存强引用和弱引用的数量,强引用用来控制管理对象的生命周期,弱引用用来控制节点的生存周期。(节点的回收在弱引用计数为零时)
注意shared_ptr对象持有的是一个强引用和一个弱引用(隐式存在),因为要同时控制对象生存周期和节点生存周期。
- 在哪里进行对象析构?
在引用计数为0时
std::shared_ptr is a smart pointer that retains shared ownership of an object through a pointer. Several shared_ptr objects may own the same object. The object is destroyed and its memory deallocated when either of the following happens
the last remaining shared_ptr owning the object is destroyed;
the last remaining shared_ptr owning the object is assigned another pointer via operator= or reset().The object is destroyed using delete-expression or a custom deleter that is supplied to shared_ptr during construction.
A shared_ptr can share ownership of an object while storing a pointer to another object. This feature can be used to point to member objects while owning the object they belong to. The stored pointer is the one accessed by get(), the dereference and the comparison operators. The managed pointer is the one passed to the deleter when use count reaches zero.A shared_ptr may also own no objects, in which case it is called empty (an empty shared_ptr may have a non-null stored pointer if the aliasing constructor was used to create it).All specializations of shared_ptr meet the requirements of CopyConstructible, CopyAssignable, and LessThanComparable and are contextually convertible to bool.All member functions (including copy constructor and copy assignment) can be called by multiple threads on different instances of shared_ptr without additional synchronization even if these instances are copies and share ownership of the same object. If multiple threads of execution access the same shared_ptr without synchronization and any of those accesses uses a non-const member function of shared_ptr then a data race will occur; the shared_ptr overloads of atomic functions can be used to prevent the data race.
template<typename T, typename Deleter = ministl::Deleter<T>>
class Data_node {
public:
Data_node() :refcnt(0), weakcnt(0), data(nullptr) {}
Data_node(T* _data) : refcnt(1), weakcnt(1), data(_data) {}
~Data_node() = default;
void incref() {
refcnt++;
}
void decref() {
assert(refcnt != 0);
refcnt--;
}
T* getData() {
return data;
}
int getRefCnt() {
return refcnt;
}
//for weak_ptr
void incweak() {
weakcnt++;
}
void desweak() {
assert(weakcnt != 0);
weakcnt--;
}
void increment() {
refcnt++, weakcnt++;
}
void decrement() {
refcnt--, weakcnt--;
check();
}
// if we need to delete data or delete ptr_ndoe
void check() {
if (refcnt == 0) {
delfunc(data);
data = nullptr;
}
if (weakcnt == 0) {
delete this;
}
}
typedef std::atomic<int> atomic_int;
Deleter delfunc;
atomic_int refcnt;
atomic_int weakcnt;
T* data;
};
template<class T, typename Deleter = ministl::Deleter<T>>
class shared_ptr
{
typedef Data_node<T, Deleter> node;
typedef Data_node<T, Deleter>* node_ptr;
typedef shared_ptr<T, Deleter> self;
private:
node_ptr ptr;
public:
shared_ptr()noexcept : ptr(nullptr)
{
}
shared_ptr(const self& x)
{
if (this->ptr != x.ptr)
{
if (ptr != nullptr)
ptr->decrement();
if (x.ptr != nullptr)
x.ptr->increment();
ptr = x.ptr;
}
}
explicit shared_ptr(T* data_ptr)
{
ptr = new node(data_ptr);
}
shared_ptr(const node_ptr _ptr) {
ptr = _ptr;
ptr->increment();
}
~shared_ptr()
{
if (ptr != nullptr)
{
ptr->decrement();
ptr = nullptr;
}
}
operator bool() {
return ptr != nullptr && ptr->refcnt != 0;
}
self& operator= (const self& x) noexcept
{
if (this->ptr == x.ptr)
return *this;
if (ptr != nullptr)
ptr->decrement();
if (x.ptr != nullptr)
x.ptr->increment();
ptr = x.ptr;
return *this;
}
T& operator*()
{
return *(ptr->data);
}
size_t use_count()
{
if (ptr == nullptr) {
return 0;
}
return ptr->count();
}
bool unique() const noexcept
{
return use_count() == 1;
}
void swap(shared_ptr& x) noexcept
{
std::swap(x.ptr, ptr);
}
void reset() noexcept
{
if (ptr == nullptr)return;
ptr->decrement();
ptr = new node();
}
//这里使用默认模板类型初始化删除器存在一个问题
//无法动态改变智能指针类型
//TODO 将删除器作为function放在指针类中
/*template <class U>
void reset(U* p)
{
if (ptr == nullptr)return;
ptr->decrement();
ptr = new Data_node<U>(p);
}*/
T* get() noexcept
{
return ptr->ptr;
}
node_ptr get_node() noexcept {
return ptr;
}
};
template<class T, class...Args>
shared_ptr<T> make_shared(Args... args)
{
return shared_ptr<T>(new T(std::forward<Args>(args)...));
}
weak_ptr
- std::weak_ptr is a smart pointer that holds a non-owning ("weak") reference to an object that is managed by std::shared_ptr. It must be converted to std::shared_ptr in order to access the referenced object.std::weak_ptr models temporary ownership: when an object needs to be accessed only if it exists, and it may be deleted at any time by someone else, std::weak_ptr is used to track the object, and it is converted to std::shared_ptr to assume temporary ownership. If the original std::shared_ptr is destroyed at this time, the object's lifetime is extended until the temporary std::shared_ptr is destroyed as well.In addition, std::weak_ptr is used to break circular references of std::shared_ptr.
解决循环计数,注意lock函数
template<class T, typename Deleter = ministl::Deleter<T>>
class weak_ptr {
typedef Data_node<T, Deleter> node;
typedef Data_node<T, Deleter>* node_ptr;
typedef shared_ptr<T, Deleter> shared;
typedef weak_ptr<T> self;
public:
weak_ptr() :ptr(nullptr) {
}
weak_ptr(const shared& rhs) {
ptr = rhs.ptr;
if (rhs.ptr)
ptr->incweak();
}
weak_ptr(const weak_ptr& r) noexcept {
ptr = r.ptr;
if (r.ptr)
ptr->incweak();
}
weak_ptr(weak_ptr&& r) noexcept {
ptr = r.ptr, r.ptr = nullptr;
}
self& operator=(const self& rhs) {
if (ptr != nullptr) {
ptr->desweak();
}
if (rhs.ptr != nullptr) {
rhs.ptr->incweak();
}
ptr = rhs.ptr;
return *this;
}
self& operator=(shared& rhs) {
auto _ptr = rhs.get_node();
if (ptr != nullptr) {
ptr->desweak();
}
if (_ptr != nullptr) {
_ptr->incweak();
}
ptr = _ptr;
return *this;
}
~weak_ptr() {
if (ptr != nullptr)
ptr->desweak();
}
int use_count() {
if (ptr == nullptr)
return 0;
return ptr->refcnt;
}
shared lock() {
return expired() ? shared_ptr<T>() : shared_ptr<T>(ptr);
}
bool expired() const noexcept {
return ptr == nullptr || ptr->refcnt == 0;
}
private:
node_ptr ptr;
};
从零开始写STL - 智能指针的更多相关文章
- 从零开始写STL—栈和队列
从零开始写STL-栈和队列 适配器模式 意图:将一个类的接口转换成客户希望的另外一个接口.适配器模式使得原本由于接口不兼容而不能一起工作的那些类可以一起工作. 主要解决:主要解决在软件系统中,常常要将 ...
- STL 智能指针
转自: https://blog.csdn.net/k346k346/article/details/81478223 STL一共给我们提供了四种智能指针:auto_ptr.unique_ptr.sh ...
- 从零开始写STL—容器—vector
从0开始写STL-容器-vector vector又称为动态数组,那么动态体现在哪里?vector和一般的数组又有什么区别?vector中各个函数的实现原理是怎样的,我们怎样使用会更高效? 以上内容我 ...
- 从零开始写STL—模板元编程之any
any class any; (since C++17) The class any describes a type-safe container for single values of any ...
- 从零开始写STL—functional
function C++11 将任意类型的可调用(Callable)对象与函数调用的特征封装到一起. 这里的类是对函数策略的封装,将函数的性质抽象成组件,便于和algorithm库配合使用 基本运算符 ...
- 从零开始写STL—模板元编程之tuple
tuple Class template std::tuple is a fixed-size collection of heterogeneous values. It is a generali ...
- 从零开始写STL—哈希表
static const int _stl_num_primes = 28; template<typename T, typename Hash = xhash<T>> cl ...
- 从零开始写STL—set/map
这一部分只要把搜索树中暴露的接口封装一下,做一些改动. set源码剖析 template<typename T> class set { public: typedef T key_typ ...
- c++智能指针(unique_ptr 、shared_ptr、weak_ptr、auto_ptr)
一.前序 什么是智能指针? ——是一个类,用来存储指针(指向动态分配对象也就是堆中对象的的指针). c++的内存管理是让很多人头疼的事,当我们写一个new语句时,一般就会立即把delete语句直接也写 ...
随机推荐
- 杨辉三角python的最佳实现方式,牛的不能再牛了
def triangles(): N = [1] while True: yield N N.append(0) N = [N[i-1] + N[i] for i in range(len(N))] ...
- ios项目中引用其他开源项目
1. 将开源项目的.xcodeproj拖入项目frameworks 2. Build Phases下 Links Binary With Libraries 引入.a文件.Target Depende ...
- XCode调试器LLDB
与调试器共舞 - LLDB 的华尔兹 你是否曾经苦恼于理解你的代码,而去尝试打印一个变量的值? NSLog(@"%@", whatIsInsideThisThing); 或者跳过一 ...
- Mac OSX简单使用中会用到的
选择操作系统(例如选择BootCamp分区的Windows):开机按住Option键直到磁盘图标出现后选择. 忘记本地账号密码:按着Command+R开机选择Recovered启动打开终端输入re ...
- js中的函数编程
之前在网上看到了一篇教你如何用js写出装逼的代码. 经过学些以及扩展很有收获在这里记录一下. 原文章找不到了.所以就不在这附上链接了. 大家看下下面两段js代码. 上面两端代码效果是一模一样的,都是在 ...
- Graveyard LA3708
白书第一章例题4 思维. 先固定一点不动,假设最后一共N个点,那么编号为0,1,...N-1, 0不动,原来的n个点分别占据i/n*N的位置(记为pos),移动到pos四舍五入的位置即可. 证明一:有 ...
- Deep_into_iris
具体ipynb文件请移步Github #各种所需要的库函数首先加载 import numpy as np import pandas as pd import matplotlib.pyplot as ...
- 《3+1团队》【Alpha】Scrum meeting 3
项目 内容 这个作业属于哪个课程 任课教师博客主页链接 这个作业的要求在哪里 作业链接地址 团队名称 3+1团队 团队博客地址 https://home.cnblogs.com/u/3-1group ...
- android问题
http://www.cnblogs.com/tianjian/category/330793.html
- 任务五:零基础HTML及CSS编码(二)
面向人群: 零基础或初学者 难度: 简单 重要说明 百度前端技术学院的课程任务是由百度前端工程师专为对前端不同掌握程度的同学设计.我们尽力保证课程内容的质量以及学习难度的合理性,但即使如此,真正决定课 ...