With Boost 1.74 and newer, use TS executor by default

[sdebionne]

Fixes #78

[daniele77]

Great. Thank you very much @sdebionne

[sdebionne]

@daniele77 Any chance to get a v1.2.1 with this fix, please?

[daniele77]

@sdebionne sure.

[daniele77]

@sdebionne the release v.1.2.1 has been published

[killerbot242]

small question, is a fundamental fix in the pipeline, instead of this define, since that can ripple up, to user code which does not want this define to switch the boost asio back to the past ?

[sdebionne]

I am not using Boost.Asio in my project and won't have time to provide a real fix unfortunately. I am not even sure what kind of effort we are talking about...

[daniele77]

@killerbot242 @sdebionne I created the issue #89 (remove the symbol BOOST_ASIO_USE_TS_EXECUTOR_AS_DEFAULT) and just fix it in commit 29fef14.
BTW: now the library can use standalone ASIO instead of BOOST ASIO. And, when you don't need remote capabilities, you don't need ASIO at all!