Subject: Re: [boost] expected/result/etc
From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2016-01-27 04:11:26
On 26 Jan 2016 at 20:19, Michael Marcin wrote:
> > I also strongly emphasise that nothing in Outcome is fixed, things
> > may yet change. Outcome is not in the Boost review queue, nor may
> > never be.
> Fair enough.
To be more specific, I am still not happy with the boilerplate macros
BOOST_OUTCOME_PROPAGATE_*, BOOST_OUTCOME_THROW_* and so on which save
typing out code which converts errors/exceptions from one type of
outcome/result/option into another, and these may yet change
There is still a bit of sloppiness in the API design of
outcome/result/option, and you'll probably notice that yourself. The
sloppiness is partially keeping options option for further reduction
of boilerplate typing, partially cruft, partially laziness.
A version of this actually presented for review here would remove
rather than add, a pared down to essentials edition would be valuable
once I completely understand what the essentials exactly are. That
said, I'm not expecting to present Outcome for entry to Boost as a
library in itself: Outcome will be an internal library for AFIO v2,
which in turn will be an internal library for my transactional
embedded key value database.
> 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
BTW I am aware the unit tests are currently failing, and I'll try to
push a fix (it's trivial) shortly. The CIs for Outcome has actually
stopped working in November, I hadn't noticed till now.
-- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk