Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce non-nullable types in reactive integrations where appropriate #3393

Merged
merged 5 commits into from
Sep 20, 2022

Commits on Aug 5, 2022

  1. Introduce non-nullable types in reactive integrations where appropriate

    * For RxJava2, use them in internal implementations where appropriate
    * For RxJava3, introduce & Any bound to generic argument in our extensions to avoid errors in Kotlin 1.8.0 due to non-nullability rx3 annotations being part of generics upper bound. This change went through commitee, and all the "unsound" declarations such as "RxSignature<Foo?>" were properly highlighted as warning that will become an error.
    qwwdfsad committed Aug 5, 2022
    Configuration menu
    Copy the full SHA
    ac0fd0e View commit details
    Browse the repository at this point in the history

Commits on Sep 20, 2022

  1. Configuration menu
    Copy the full SHA
    34c08dd View commit details
    Browse the repository at this point in the history
  2. ~

    qwwdfsad committed Sep 20, 2022
    Configuration menu
    Copy the full SHA
    508ce3a View commit details
    Browse the repository at this point in the history
  3. ~

    qwwdfsad committed Sep 20, 2022
    Configuration menu
    Copy the full SHA
    6b6fbd2 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    fa472f9 View commit details
    Browse the repository at this point in the history