I'm all for this also, i think at minimum we should take advantage of what we get for free from c++11, especially since we have c++11 checks in our autoconf script already anyway. I had never actually heard of concurrencykit until now. I know TBB isn't really an option, but has anyone compared the performance of the data structures of TBB to concurrencykit?
But don't let any of that stop you guys from reviewing this patch ;) Brian On Mar 8, 2013, at 8:18 AM, John Plevyak <jplev...@gmail.com> wrote: > +1 > On Mar 8, 2013 6:39 AM, "Leif Hedstrom" <zw...@apache.org> wrote: > >> On 3/8/13 4:24 AM, Theo Schlossnagle wrote: >> >>> Would we consider just pulling in concurrencykit? We'll get this and many >>> other composed primitives from an active community for free. >> >> I discussed this with John a while ago, and we both agreed it'd be >> desirable to use this instead of rolling our own. >> >> So +1 from me at least (obviously with careful benchmarking etc.). >> >> Also, I'd suggest we do it for 3.5.x, i.e. lets get 3.4 rolled out in our >> normal release time frame (june). I'm writing up the roadmap for v3.4 as we >> discussed at ACNA, and will email the mailing list today with the proposal >> at hand. >> >> Cheers, >> >> >> -- Leif >> >>
