mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] asfgit closed pull request #315: fix Disarding a Future -> Discarding a Future
Date Thu, 25 Oct 2018 16:00:19 GMT
asfgit closed pull request #315: fix Disarding a Future -> Discarding a Future

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/3rdparty/libprocess/ b/3rdparty/libprocess/
index 36370440c0..3e3d5e716d 100644
--- a/3rdparty/libprocess/
+++ b/3rdparty/libprocess/
@@ -103,7 +103,7 @@ The following table is meant to capture these transitions:
throughout our examples. See [`CHECK()` Overloads](#futures-and-promises-check-overloads)
for more details about these macros.
-### <a name="futures-and-promises-discarding-a-future"></a> Disarding a Future
(aka Cancellation)
+### <a name="futures-and-promises-discarding-a-future"></a> Discarding a Future
(aka Cancellation)
 You can "cancel" the result of some asynchronous operation by discarding a future. Unlike
doing a discard on a promise, _discarding a future is a request that may or may not be be
satisfiable_. You discard a future using `Future::discard()`. You can determine if a future
has a discard request by using `Future::hasDiscard()` or set up a callback using `Future::onDiscard()`.
Here's an example:


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message