Re: [boost] expected/result/etc

Subject: Re: [boost] expected/result/etc
From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2016-02-03 04:10:09

On 2 Feb 2016 at 22:25, Michael Marcin wrote:

> >> Would you like feedback on it if I use it anyways?
> >
> > Oh yes please, the futurey stuff has some definite showstopper bugs
> > but the remainder I currently believe to be ready for feedback from
> > others.
> 
> FYI it generates some noise when using:
> #include <boost/outcome/monad.hpp>
> #include <boost/log/trivial.hpp>
> 
> 2>C:\code\boost\boost_1_60_0\boost/move/core.hpp(341): warning C4005: 
> 'BOOST_RV_REF': macro redefinition
> 2> 
> c:\code\boost\boost_1_60_0\boost\outcome\v1\../bindlib/include/boost/config.hpp(197): 
> note: see previous definition of 'BOOST_RV_REF'
> 2>C:\code\boost\boost_1_60_0\boost/move/core.hpp(379): warning C4005: 
> 'BOOST_COPY_ASSIGN_REF': macro redefinition
> 2> 
> c:\code\boost\boost_1_60_0\boost\outcome\v1\../bindlib/include/boost/config.hpp(201): 
> note: see previous definition of 'BOOST_COPY_ASSIGN_REF'
> 2>C:\code\boost\boost_1_60_0\boost/move/core.hpp(385): warning C4005: 
> 'BOOST_FWD_REF': macro redefinition
> 2> 
> c:\code\boost\boost_1_60_0\boost\outcome\v1\../bindlib/include/boost/config.hpp(193): 
> note: see previous definition of 'BOOST_FWD_REF'
> 
> 
> You might've already noticed I guess because reversing the includes 
> makes it shut up.

You're using Outcome in standalone non-Boost configuration in 
combination with Boost, so the "Boost-lite" emulation it configures 
will collide with Boost.

As you noticed if you include Outcome after Boost it spots you've 
already included Boost and turns standalone off.

You can configure Outcome to use Boost natively from the get go via 
macros. See its config.hpp. Or just keep including Outcome after all 
other Boost headers.

Niall

-- 
ned Productions Limited Consulting
http://www.nedproductions.biz/ 
http://ie.linkedin.com/in/nialldouglas/