Hi, @ilpropheta !

Your example:

env.environment().introduce_coop([&](so_5::coop_t& c) {
       auto tpool = so_5::disp::thread_pool::make_dispatcher(env.environment(), 4);
       c.make_agent_with_binder<test>(
             tpool.binder(), // expected
             tpool.binder(),  // weird to pass twice...
            ... other stuff ...);
});

can be rewritten this way:

auto tpool = so_5::disp::thread_pool::make_dispatcher(env.environment(), 4);
env.environment().introduce_coop(
   tpool.binder() /* the default binder for the whole coop */,
   [&](so_5::coop_t& c) {
       // There is no need to call make_agent_with_binder because
       // the new agent will use the default binder for the coop.
       c.make_agent<test>(
         tpool.binder(),  // expected...
         ... other stuff ...);
    });

but I understand that there can be cases when the parent coop uses one default dispatcher binder, but an agent in it uses another dispatcher binder.

So I think that it's possible to add two new methods:

so_5::coop_t::default_coop_binder() that returns the default binder for the coop (the default binder for a coop can be specified via so_5::environment_t::make_coop() method);
so_5::agent_t::so_this_agent_disp_binder() that returns the binder used for the agent.

And we'll have a possibility to write this way:

so_environment().introduce_coop(
   // Use the same binder as our coop.
   so_coop().default_coop_binder(),
   [&](so_5::coop_t & coop) {
      coop.make_agent<test>(...);
   });

or that way:

so_environment().introduce_coop( // No explicit default coop binder.
   [&](so_5::coop_t & coop) {
      coop.make_agent_with_binder<test>(
         // Use the binder that was used for the agent.
         so_this_agent_disp_binder(),
         ...);
   });

NOTE. Since v.5.8 the method so_this_agent_disp_binder() can easily be implemented because the agent's binder is now stored inside so_5::agent_t.

Default dispatcher binder of child coops #14

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions