raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 11

Remove "Future is a monad" title (#25437)

Browse source 
* Add explanation for Future breaking monad laws

* Update futures.md
This commit is contained in:
Jakub Kozłowski 2018-08-07 08:14:06 +02:00 • committed by Konrad `ktoso` Malawski
parent a0e79a0542
commit d014877786
1 changed files with 0 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
akka-docs/src/main/paradox/futures.md
View file

@ -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: