5 Dec
2019
5 Dec
'19
3:16 p.m.
Could someone please have a look at http://boost.2283326.n4.nabble.com/release-proto-MSVC-19-24-28314-VS-2019-16... cause it's a showstopper for the latest VS 2019 (16.4.0). It's not an error introduced in 1.72 but already there for a long time, and now the latest MSVC version produces an error on that MSVC-workaround. thanks -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Dev-f2600599.html