Subject: Re: [boost] [review] Review of Outcome (starts Fri-19-May)
From: Peter Dimov (lists_at_[hidden])
Date: 2017-05-19 22:18:32
Niall Douglas wrote:
> > In the event the library is accepted, what will the contents of the
> > repository boostorg/outcome be, and what will end up in the Boost
> > release under libs/outcome?
> That depends on what conditions the review manager places on acceptance,
> if acceptance is recommended.
Yes of course. My question was what you intend to happen.
> As I've mentioned before, during build we assemble a single file include
> of all the dependencies, including those parts of boost-lite needed. There
> is therefore no strict need to ship boost-lite in any boostorg repo, which
> is good as I believe boostorg currently doesn't support project level
This would only work if I use boost/outcome/outcome_v1.0.hpp, right? The
headers in v1.0/ do not compile without boost-lite.
> To be honest, I don't think it hugely important how we get Outcome into
An interesting position. I, however, in order to decide between Yes and No,
need to know what, precisely, will happen on Yes.
Of course I could say Yes if you do such and so, otherwise No, but it's good
to know how you see things and what's your intent.
> > As I already asked, will boostorg/outcome be the primary source
> > repository for Boost.Outcome? If there is a PR submitted against
> > boostorg/outcome, what steps will need to be performed in order for that
> > PR to become integrated into the Outcome code base?
> I'd prefer not a script generated boostorg/outcome repo, it makes
> maintenance harder.
I'm not sure I understand. If you prefer not a script-generated
boostorg/outcome repo, what do you prefer?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk