You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ The library provides an implementation of the [CompletionStage](https://docs.ora
4
4
5
5
Since the version [0.7.0](https://github.com/vsilaev/tascalate-concurrent/releases/tag/0.7.0) the library is shipped as a multi-release JAR and may be used both with Java 8 as a classpath library or with Java 9+ as a module.
6
6
7
-
IMPORTANT!
7
+
**IMPORTANT!**
8
8
9
9
In the version [0.8.0](https://github.com/vsilaev/tascalate-concurrent/releases/tag/0.8.0) the artifact was renamed:
10
10
New name:
@@ -23,7 +23,8 @@ Old Name
23
23
<version>0.7.1</version>
24
24
</dependency>
25
25
```
26
-
26
+
**IMPORTANT!**
27
+
Don't use release 0.9.0, use [0.9.1](https://github.com/vsilaev/tascalate-concurrent/releases/tag/0.9.1) instead -- the previous one is severely broken, see release notes for 0.9.1.
27
28
28
29
# Why a CompletableFuture is not enough?
29
30
There are several shortcomings associated with [CompletableFuture](https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html) implementation that complicate its usage for real-life asynchronous programming, especially when you have to work with I/O-bound interruptible tasks:
0 commit comments