1

Topic: boost 1.66

On 1.66 someone already skipped?
Broke nothing? asio and thread they it is strong %...

2

Re: boost 1.66

PPA;
In Asio some out-of-date names renamed final. But semantics remained former.
Thread and other  - it was not necessary  the code.
In  it is not used yet, but tests did not break.

3

Re: boost 1.66

Anatoly Moskovsky wrote:

PPA;
In Asio some out-of-date names renamed final. But semantics remained former.
Thread and other  - it was not necessary  the code.
In  it is not used yet, but tests did not break.

And  they what use now in Asio, old Coroutine or new Coroutine2?
And what plans at them in this respect?
Like as old Coroutine using API from boost.context already deprecated for a long time.

4

Re: boost 1.66

Utkin wrote:

And  they what use now in Asio, old Coroutine or new Coroutine2?

Inside did not look. And outside it is not visible.

5

Re: boost 1.66

Anatoly Moskovsky wrote:

it is passed...
Inside did not look. And outside it is not visible.

Looked - old Coroutine use in Boost. Asio 1.66. They more year as Deprecated, since Boost 1.62 (September 2016), and all in any way do not replace them.
Very much brake with development that the standard that Boost.

6

Re: boost 1.66

Vasja Utkin;
And what for to change that that works?))

7

Re: boost 1.66

Anatoly Moskovsky wrote:

Vasja Utkin;
And what for to change that that works?))

It is a question to those who Coroutine made deprecated smile
In the standard accept only Coroutine2 (stackful) and-or Await-CO2 (stackless): https://github.com/jamboree/co2#performance
And than earlier Boost. Asio passes on Coroutine2 - i.e. the longer on it it will be tested by community, the earlier Asio gets to the standard. If to 2020 Boost. Asio will be on Coroutine in C standard ++ 20 it not to see.

8

Re: boost 1.66

Vasja Utkin;
Judging by  Asio on  this question of very few people excites. So it is not enough chances)