[outcome v2] Proposed second review dates?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[outcome v2] Proposed second review dates?

Boost - Dev mailing list
Dear all,

Now that the DoubleEnded review has finished, can I poll for preferred
dates for a second Outcome review? Options:

1. Friday 1st December until Monday 11th December?

2. Friday 19th January until Monday 29th January?

The reason for the delay is that the documentation writers are committed
to other stuff until mid-November, plus there is the US Thanksgiving.
Other than documentation, the library is ready to go at
https://github.com/ned14/boost-outcome.

Niall

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


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [outcome v2] Proposed second review dates?

Boost - Dev mailing list
Le 09/10/2017 à 15:04, Niall Douglas via Boost a écrit :

> Dear all,
>
> Now that the DoubleEnded review has finished, can I poll for preferred
> dates for a second Outcome review? Options:
>
> 1. Friday 1st December until Monday 11th December?
>
> 2. Friday 19th January until Monday 29th January?
>
> The reason for the delay is that the documentation writers are committed
> to other stuff until mid-November, plus there is the US Thanksgiving.
> Other than documentation, the library is ready to go at
> https://github.com/ned14/boost-outcome.
>
>
>
Both are good for me :(


If it is not yet ready, maybe January would give you more time. Up to
you and the review manager.

Vicente


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [outcome v2] Proposed second review dates?

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Mon, Oct 9, 2017 at 6:04 AM, Niall Douglas via Boost
<[hidden email]> wrote:
> 1. Friday 1st December until Monday 11th December?

Do these dates overlap with the release for 1.66.0?

Thanks

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [outcome v2] Proposed second review dates?

Boost - Dev mailing list
>> 1. Friday 1st December until Monday 11th December?
>
> Do these dates overlap with the release for 1.66.0?

They do.

As v2 Outcome is basically what I thought the consensus from the v1
review wanted, in theory it's a box ticking exercise which will involve
no debate nor much discussion here.

:)

But that's also why I am asking which proposed dates people prefer?

Niall

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


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [outcome v2] Proposed second review dates?

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
> If it is not yet ready, maybe January would give you more time. Up to
> you and the review manager.

Is that you voting in favour of January?

Niall

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


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [outcome v2] Proposed second review dates?

Boost - Dev mailing list
On Tue, Oct 10, 2017 at 6:38 AM, Niall Douglas via Boost
<[hidden email]> wrote:
> Is that you voting in favour of January?

I'm not sure I have a horse in this race, is boost::expected part of Outcome?

Thanks

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [outcome v2] Proposed second review dates?

Boost - Dev mailing list
>> Is that you voting in favour of January?
>
> I'm not sure I have a horse in this race, is boost::expected part of Outcome?

It can be if reviewers wish it. See
https://ned14.github.io/outcome/faq/#how-far-away-from-the-proposed-std-expected-t-e-is-outcome-s-checked-t-e.
There is an implementation in the test suite.

You may remember that the v1 Outcome review didn't like Expected much
either. The consensus at that time wanted something different which I
believe is the v2 I am proposing.

I am in similar boat to you Vinnie. I hope to submit AFIO as the File
I/O TS next year. Every single API uses outcome::result, and in TS form
will need to be std::expected instead. You'll note v2 Outcome has been
carefully designed to allow that to work, so Boost gets its desired
"alt-Expected" whilst library code like AFIO isn't impacted.

If Outcome v2 is accepted, I already foresee legions of complaining
users about the differences. But I hate to be blunt, I think Boost is
right and WG21 is wrong. We thought about it much more deeply last May
than WG21 whose deep discussion time is limited, and I think it really
shows.

Niall

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


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost