Boost Users :
From: Stephan Menzel (stephan.menzel_at_[hidden])
Date: 2019-09-03 05:09:56
Hello Christian and Mario, thanks for your responses.
I think I'm much closer to an implementation now.
Am Mo., 2. Sept. 2019 um 13:57 Uhr schrieb Cristian Morales Vega <
> > I would also appreciate any hints in general about own composed
> operations. Perhaps there are other approaches that are a bit less
> Once you get used to it it's not really that intimidating. All the
> composed operations follow the same pattern and other than the
> "operator()" it's a lot of repetitive boilerplate, quite boring
Yes, as I was moving forward this turnes out to be the problem now.
Essentially, most of the operations I have in mind combine tasks with
different completion token types. For example async_resolve() and
Once I saw how operator() basically acts as a handler for all the async ops
within this question became the most interesting one.
> If you look at
> you will find a whole "Writing Composed Operations" section in the
I did have a look at Vince's tutorial but tbh I wanted so see the problems
that would be simplified first before jump right ahead.
I guess that's where I'm now ;-)
Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net