mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominic Hamon" <dha...@twopensource.com>
Subject Re: Review Request 27826: Future::failure should have a const ref return.
Date Mon, 10 Nov 2014 22:26:27 GMT


> On Nov. 10, 2014, 1:50 p.m., Ben Mahler wrote:
> > 3rdparty/libprocess/include/process/future.hpp, line 1186
> > <https://reviews.apache.org/r/27826/diff/2/?file=757271#file757271line1186>
> >
> >     Can we avoid the need for this with a separate change to use ABORT when failure()
is called on a non-failed future? Much like we do for try, result, option.

https://reviews.apache.org/r/27831/


- Dominic


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/27826/#review60686
-----------------------------------------------------------


On Nov. 10, 2014, 1:12 p.m., Dominic Hamon wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/27826/
> -----------------------------------------------------------
> 
> (Updated Nov. 10, 2014, 1:12 p.m.)
> 
> 
> Review request for mesos and Ben Mahler.
> 
> 
> Bugs: MESOS-1694
>     https://issues.apache.org/jira/browse/MESOS-1694
> 
> 
> Repository: mesos-git
> 
> 
> Description
> -------
> 
> see summary
> 
> 
> Diffs
> -----
> 
>   3rdparty/libprocess/include/process/future.hpp 46ae16b0bbce79005f5ed8711be663eeeb8f4bcf

> 
> Diff: https://reviews.apache.org/r/27826/diff/
> 
> 
> Testing
> -------
> 
> make check.
> manual review of calling code.
> 
> 
> Thanks,
> 
> Dominic Hamon
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message