David Karnok

No. 1. Check out the 2.x branch 2. Create a new branch of of 2.x named `JavadocCleanup_1203` 3. Open the [changed files](https://github.com/ReactiveX/RxJava/pull/6729/files) of #6729 in a browser 4. For each...

@skywall Updated.

These two could use the restyling: - https://github.com/ReactiveX/RxJava/blob/3.x/docs/Conditional-and-Boolean-Operators.md - https://github.com/ReactiveX/RxJava/blob/3.x/docs/Observable-Utility-Operators.md

I did a different implementation but the degradation isn't gone, just reduced:  With the new code organization, the performance is slightly worse at P=1 and P=6 and somewhat better...

If I implement batch-dispatching, the the scheduling overhead appears to be mostly eliminated: 

Might be possible to write a check for this but currently the source file is not parsed but only string-contains checked.

@MiSikora IntelliJ/Kotlin users are mostly affected by their lack, or sometimes their presence so I can't give you a definite answer from a Eclipse/Java perspective.

There is no ordering between group emission and cancellation and the JavaDocs warns about MBEs due to lack of requesting more groups. http://reactivex.io/RxJava/3.x/javadoc/io/reactivex/rxjava3/core/Flowable.html#groupBy-io.reactivex.rxjava3.functions.Function- > Backpressure: > The consumer of the...

It's more complicated than that. The request/delivery in the inner groups still feed back to the main source because they have to trigger progress if they become ready. Consequently, since...

Anything not checked is open for grabs. The list also hints about what should be done. The ones where only label needs to change are the easiest. Use any pixel...