From d01487778652d92bfe1edbf1eb7c53b4de04a2b0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Koz=C5=82owski?= Date: Tue, 7 Aug 2018 08:14:06 +0200 Subject: [PATCH] Remove "Future is a monad" title (#25437) * Add explanation for Future breaking monad laws * Update futures.md --- akka-docs/src/main/paradox/futures.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/akka-docs/src/main/paradox/futures.md b/akka-docs/src/main/paradox/futures.md index 2908be4df3..9f0a260ba6 100644 --- a/akka-docs/src/main/paradox/futures.md +++ b/akka-docs/src/main/paradox/futures.md @@ -155,8 +155,6 @@ For these examples `PrintResult` is defined as follows: Scala's `Future` has several monadic methods that are very similar to the ones used by Scala's collections. These allow you to create 'pipelines' or 'streams' that the result will travel through. -### Future is a Monad - The first method for working with `Future` functionally is `map`. This method takes a @scala[`Function`]@java[`Mapper`] which performs some operation on the result of the `Future`, and returning a new result. The return value of the `map` method is another `Future` that will contain the new result: