You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by bb...@apache.org on 2018/06/25 08:18:03 UTC
mesos git commit: Fixed formatting in libprocess `README`.
Repository: mesos
Updated Branches:
refs/heads/master 3228db4ac -> d22a3d701
Fixed formatting in libprocess `README`.
The table columns were misaligned due to missing
whitespace.
Review: https://reviews.apache.org/r/67719/
Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/d22a3d70
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/d22a3d70
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/d22a3d70
Branch: refs/heads/master
Commit: d22a3d7015567de11b3e96a5a686e65dea04aca1
Parents: 3228db4
Author: Benno Evers <be...@mesosphere.com>
Authored: Mon Jun 25 10:14:51 2018 +0200
Committer: Benjamin Bannier <bb...@apache.org>
Committed: Mon Jun 25 10:16:42 2018 +0200
----------------------------------------------------------------------
3rdparty/libprocess/README.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos/blob/d22a3d70/3rdparty/libprocess/README.md
----------------------------------------------------------------------
diff --git a/3rdparty/libprocess/README.md b/3rdparty/libprocess/README.md
index d8b28fa..9846ece 100644
--- a/3rdparty/libprocess/README.md
+++ b/3rdparty/libprocess/README.md
@@ -85,11 +85,11 @@ You can also add a callback to be invoked when (or if) a transition occurs (or h
The following table is meant to capture these transitions:
-| Transition | `Promise::*()` | `Future::is*()` | `Future::on*()` |
-| ------ | -------------- | --------------- | --------------- |
-| `READY` | `Promise::set(T)` | `Future::isReady()` | `Future::onReady(F&&)` |
-| `FAILED` | `Promise::fail(const std::string&)` | `Future::isFailed()` | `Future::onFailed(F&&)` |
-| `DISCARDED` | `Promise::discard()` | `Future::isDiscarded()` | `Future::onDiscarded(F&&)` |
+| Transition | `Promise::*()` | `Future::is*()` | `Future::on*()` |
+| ----------- | ----------------------------------- | ----------------------- | -------------------------- |
+| `READY` | `Promise::set(T)` | `Future::isReady()` | `Future::onReady(F&&)` |
+| `FAILED` | `Promise::fail(const std::string&)` | `Future::isFailed()` | `Future::onFailed(F&&)` |
+| `DISCARDED` | `Promise::discard()` | `Future::isDiscarded()` | `Future::onDiscarded(F&&)` |
> <br> Code Style: prefer [composition](#futures-and-promises-composition) using `Future::then()` and `Future::recover()` over `Future::onReady()`, `Future::onFailed()`, `Future::onDiscarded()`, and `Future::onAny()`. A good rule of thumb is if you find yourself creating your own instance of a `Promise` to compose an asynchronous operation you should use [composition](#futures-and-promises-composition) instead! <br><br>