From: Tobias Loew (Tobias.Loew_at_[hidden])
Date: 2019-12-05 15:16:44
Could someone please have a look at
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.
-- Sent from: http://boost.2283326.n4.nabble.com/Boost-Dev-f2600599.html
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk