Re: [boost] [review] **NEXT WEEK** Review of Outcome (starts Fri-19-May)

Subject: Re: [boost] [review] **NEXT WEEK** Review of Outcome (starts Fri-19-May)
From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2017-05-14 18:24:03

>> About a year ago when I was considering whether to invest the
>> considerable effort to bring Outcome into a Boost ready form I asked
>> here about internal sublibraries.
>>
>> Apparently some years ago they were common enough in submitted new Boost
>> libraries, and indeed some internal sublibraries went on to later become
>> Boost libraries in their own right.
>>
>> We should proceed here with the Outcome review the same way as it was
>> with those preceding cases. Whatever the precedent is.
>>
>> (I'm not sure what the exact precedent is, whomever knows for sure
>> please speak, but be aware that most of the dependency on boost-lite is
>> substitutable for Boost proper)
> 
> I'm not sure I understand what you mean. You're submitting a library
> for review. Everything in the library is subject to review - the
> design, the implementation, the documentation, the tests.
> 
> The implementation of Outcome includes something called boost-lite
> right now. Reviewers are allowed to review any files in this
> boost-lite, just as they review any implementation detail of Outcome,
> right?

It's up to the reviewer as to how much to review or not.

Whatever constructive feedback they have, irrespective of whether
Outcome uses that part or not, I'll gladly take it. I would say it may
make Charley's life tough to disambiguate feedback though.

Niall

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