指向 this 的回调智能指针,以便对象在回调中保持活动状态

如何解决指向 this 的回调智能指针,以便对象在回调中保持活动状态

高达 C++17

我想确保对象在其回调运行期间一直处于活动状态。

这是重要的一点。考虑一个回调函数,它需要来自发出回调的对象的数据。现在我希望让发射对象保持活动状态,直到所说的回调函数得到它需要的东西。这可能不是所有回调的情况,并非所有回调都处理接下来可能被删除的对象。

这是我想出来的。使用命名构造函数习惯用法,我可以确保创建的对象是一个 shared_ptr,然后我可以将一个 weak_ptr 用于它等等。

我想知道是否有更好的方法来解决这个问题?

// Example program
#include <memory>
#include <functional>
#include <iostream>

class Callback
{
public:
  using t_callback_func = std::function<void(std::shared_ptr < Callback>)>;
  using t_shared = std::shared_ptr<Callback>;
  std::vector<t_callback_func> callbacks;
  std::weak_ptr<Callback> uglyhax;

  static std::shared_ptr<Callback> make()
  {
    auto shared = std::shared_ptr<Callback>(new Callback());
    shared->uglyhax = shared;
    return shared; 
  }

  void register_callback(std::function<void(std::shared_ptr<Callback>)> && p_callback)
  {
    callbacks.emplace_back(std::forward<t_callback_func>(p_callback));
  }

  void notify()
  {
    if (auto shared = uglyhax.lock())
    {
      for (auto & callback : callbacks)
      {
        callback(shared);
      }
    }
  }

  void remove_callbacks()
  {
    callbacks.clear();
  }

  void hello()
  {
    std::cout << "hello " << this << "\n";
  }

  ~Callback() { std::cout << "dtor  " << this << "\n"; }

protected:
  Callback() { std::cout << "ctor " << this << "\n"; }

};

class EventList
{
  std::vector<std::function<void()>> events;
public:
  void call_events()
  {
    for (auto& event : events)
    {
      event();
    }
    events.clear();
  }

  template<class ...Args>
  auto wrap_as_event(std::function<void(Args...)> && p_func)
  {
    return [this,p_func](Args... args)
    {
      std::cout << "adding event\n";
      this->events.emplace_back(std::move(std::bind(std::move(p_func),std::forward<Args>(args)...)));
    };
  }
};

int main()
{
  EventList list;
  {
    {
      auto thing = Callback::make(); // I want to keep the thing allocated here alive until all its callbacks have been processed
      std::function<void(Callback::t_shared)> function = [](Callback::t_shared ptr) {ptr->hello(); ptr->remove_callbacks(); };
      thing->register_callback(list.wrap_as_event(std::move(function)));
      thing->notify();
    }
    std::cout << "dtor should be called after this\n";
    list.call_events();
  }
  std::cout << "dtor should be called before this\n";
}

输出:

ctor 013E81C0
adding event
dtor should be called after this
hello 013E81C0
dtor  013E81C0
dtor should be called before this

解决方法

您可以将事件执行的逻辑与事件和事件负载对象分开。

Callable 继承了 enable_shared_from_this<Callable>,允许安全创建额外的 shared_ptr。工厂方法 getCallable 将在堆上创建一个 Callable 实例,这是 enible_shared_from_this 工作的先决条件。

Callable 类知道如何生成事件以及如何将它的 shared_ptr 注册到 CallableEvent 中,Event 是专门的 Event 类。然后将 EventHandler 发送到将处理事件的 // Example program #include <memory> #include <functional> #include <iostream> #include <vector> class Event; class Callable; class CallableEvent; class Event { public: virtual void trigger(); }; class EventHandler { public: std::vector<std::shared_ptr<Event>> eventList; static EventHandler& getInstance() { static EventHandler instance = EventHandler(); return instance; } void registerEvent(std::shared_ptr<Event> event) { eventList.push_back(event); } void processEvents() { for (auto event : eventList) { event->trigger(); } } }; class CallableEvent : public Event,public std::enable_shared_from_this<CallableEvent> { public: using t_callback = std::function<void(std::shared_ptr<Callable>)>; std::shared_ptr<Callable> callable; t_callback callback; void trigger() override; CallableEvent() { std::cout << "Callable Event Created " << this << "\n"; } ~CallableEvent() { std::cout << "Callable Event Destroyed " << this << "\n"; } }; class Callable : public std::enable_shared_from_this<Callable> { public: int _payload; void registerEvent(std::function<void(std::shared_ptr<Callable>)> lambda) { std::shared_ptr<CallableEvent> ev = std::shared_ptr<CallableEvent>(new CallableEvent()); ev->callable = shared_from_this(); ev->callback = std::move(lambda); EventHandler::getInstance().registerEvent(ev); } static std::shared_ptr<Callable> createCallable(int payload) { return std::shared_ptr<Callable>(new Callable(payload)); } void sayThis() { std::cout << "Hello from Callable "<< this << " my payload is " << _payload << "\n"; } ~Callable() { std::cout << "Callable destroyed " << this << " with payload " << _payload << "\n"; } private: Callable(int payload) { _payload = payload; std::cout << "Callable created " << this << " with payload " << _payload << "\n"; } }; void Event::trigger() { std::cout << "generic event \n"; } void CallableEvent::trigger() { callback(callable); } int main() { { { auto cb = Callable::createCallable(15); CallableEvent::t_callback function = [](std::shared_ptr<Callable> ptr) { std::cout << "Calling from lambda\n"; ptr->sayThis(); }; cb->registerEvent(function); } std::cout << "Callback should be called after this\n"; EventHandler::getInstance().processEvents(); } std::cout << "Callback should be called before this\n"; }

Callable created 0x7f89f4c057d0 with payload 15
Callable Event Created 0x7f89f4c05810
Callback should be called after this
Calling from lambda
Hello from Callable 0x7f89f4c057d0 my payload is 15
Callback should be called before this
Callable Event Destroyed 0x7f89f4c05810
Callable destroyed 0x7f89f4c057d0 with payload 15

Process finished with exit code 0

运行示例时,会生成以下输出:

UIDocumentInteractionController

现在您可以将处理程序移动到另一个线程,并且事件将异步执行。

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-