2.x: Consumer contract is violated when using doOnEvent

[ansman]

The following code showcases the problem:

Completable.complete()
  .doOnEvent(t -> {})

t in this case is annotated with @NonNull but it will be null since the completable completes.

This is a real pain in Kotlin since the following code crashes in runtime:

Completable.complete()
  .doOnEvent {}

[sakuna63]

BiConsumer is also violated when using Single#subscribe. Either value or throwable will be null.

[akarnokd]

Removing the annotation from Consumer may affect all other places where it is not-null. Can you override the annotation somehow at the call site?

@sakuna63 BiConsumer doesn't have the annotations.

[svenjacobs]

I just stumbled upon this while using Kotlin, too. However I wonder how a function argument annotated with @NonNull can ever be null? Even in Java this should be problematic as the contract is broken.

[akarnokd]

Maybe RxKotlin has/could have workarounds for these. /cc @thomasnield

[sakuna63]

Sorry, I read old source code.
The annotations have already been removed at #5257

[svenjacobs]

This was introduced with #5023

[svenjacobs]

Removing the annotation from Consumer may affect all other places where it is not-null. Can you override the annotation somehow at the call site?

@akarnokd If there's just one call that passes null to the function then imho the argument must be annotated with @Nullable and not @NonNull. What's the point of @NonNull when it can be null?

[ansman]

@akarnokd no, the problem cannot be remidied in kotlin which completely prevents the usage of that operator in kotlin.
Removing the annotation won't make it nullable though, it would just mean that we don't know the nullability status which is the case too. Why is it important to keep it? I see very little harm in removing it and as @svenjacobs said the contract is broken in java too. If I were to null check it in java I would probably get lint warning telling me to remove the null check.
Ideally there should be multiple interfaces like @rharter suggested in the issue for BiFunction

[akarnokd]

If you can think you can resolve this with minimal changes, PR welcome.

[svenjacobs]

By the way this issue emerged with the release of Kotlin 1.1.3. Although @NonNull has already been added months ago it seems that the compiler/runtime library of Kotlin 1.1.3 became stricter in regards to nullability.