On 9/4/2015 4:19 PM, Oliver Kowalke wrote:
2015-09-04 21:09 GMT+02:00 Agustín K-ballo Bergé
: - All of `future` and `shared_future` https://github.com/olk/boost-fiber/blob/master/include/boost/fiber/future/fu...
- All of `shared_state` https://github.com/olk/boost-fiber/blob/master/include/boost/fiber/future/de...
- All of `promise` https://github.com/olk/boost-fiber/blob/master/include/boost/fiber/future/pr...
- All of `task_object` https://github.com/olk/boost-fiber/blob/master/include/boost/fiber/future/de...
For each of them, there is only one function that varies amongst specializations. Moving common code to a helper base class will make the code readable, easier to maintain, and reduce the bloating.
OK, you refer to template specializations of future, promise etc. I prefer to prevent additional indirections introduced by deriving from base classes
What additional indirections would deriving from a base class introduce? Regards, -- Agustín K-ballo Bergé.- http://talesofcpp.fusionfenix.com