kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #36753
Re: Do we actually need our own coroutine library?
Simon,
If we could depend on boost to stop changing their coroutine code every
couple of version then we wouldn't have to fork it and maintain our own
version. Unfortunately, history has proven otherwise. Your change
would be the forth time this code as been changed to accommodate boost.
The short answer is yes, we actually need our own coroutine code because
we cannot depend on boost to not cut us off at the knees every few
versions. Maybe when couroutines are available in the standard c++
library, then we can get rid of our library. Please do not change
coroutine code without a really good reason.
Cheers,
Wayne
On 07/22/2018 04:47 PM, Simon Richter wrote:
> Hi,
>
> the MSVC builds have reverted the coroutine patches for quite some time
> now, and it seems to work unless you attempt to compile against Boost 1.61.
>
> Here's the current coroutine related stack on the msvc branch. Does this
> break anything for anyone?
>
> Simon
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
References