Skip to content

Commit 894cb55

Browse files
authored
Update README.md
1 parent 1d6e211 commit 894cb55

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -223,9 +223,9 @@ Performance-wise suspendable methods behaves the same as asynchronous task metho
223223
Implemenation notes: technically suspendable methods are implemented as continuable methods that follow rules defined by [Tascalate JavaFlow](https://github.com/vsilaev/tascalate-javaflow) library, so you may use any continuable annotation that is supported by Tascalate JavaFlow, not only `@suspendable`.
224224

225225
# Generators
226+
TDB
226227

227228
# Scheduler & SchedulerResolver - where is my code executed?
228-
# SchedulerResolver - what Scheduler to use?
229229
## Introducing schedulers
230230
When executing asynchronous code with `CompletionStage` / `CompletableFuture` it's critical to know where the code is resumed once the corresponding completion stage is settled. With regular `CompletionStage` API the answer is pretty straightforward: the code will be resumed with the `Executor` supplied as an additional parameter to the API method like below:
231231
```java

0 commit comments

Comments
 (0)