Skip to content

Commit 63572c7

Browse files
authored
Fix broken table in "Using an overload with ..."
1 parent fd47265 commit 63572c7

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -392,9 +392,10 @@ allow further customization of the backpressure behavior.
392392
Many frequently used operator has overloads that can deal with the other types. These are usually named with the suffix of the target type:
393393

394394
| Operator | Overloads |
395+
|----------|-----------|
395396
| `flatMap` | `flatMapSingle`, `flatMapMaybe`, `flatMapCompletable`, `flatMapIterable` |
396397
| `concatMap` | `concatMapSingle`, `concatMapMaybe`, `concatMapCompletable`, `concatMapIterable` |
397-
| `switchMap` | `switchMapSingle`, `switchMapMaybe`, `switchMapCompletable`, `switchMapIterable` |
398+
| `switchMap` | `switchMapSingle`, `switchMapMaybe`, `switchMapCompletable` |
398399

399400
The reason these operators have a suffix instead of simply having the same name with different signature is type erasure. Java doesn't consider signatures such as `operator(Function<T, Single<R>>)` and `operator(Function<T, Maybe<R>>)` different (unlike C#) and due to erasure, the two `operator`s would end up as duplicate methods with the same signature.
400401

0 commit comments

Comments
 (0)