13 Dec
2017
13 Dec
'17
11:51 p.m.
On 13 December 2017 at 23:43, Gavin Lambert via Boost
On 13/12/2017 23:24, Daniel James wrote:
I haven't got the binaries installed yet, so I haven't reproduced it, but I think it's caused because timer now includes the chrono headers using BOOST_CHRONO_HEADER_ONLY, and in the chrono inlined headers not all functions are BOOST_CHRONO_INLINE. It looks like this problem was always in chrono, but BOOST_CHRONO_HEADER_ONLY was widely used enough for it to be detected.
I'm having trouble parsing this. I think you're missing some negations somewhere.
Should have been "wasn't widely used".