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

1.x: fix scan() not accepting a null initial value #3485

Merged
merged 1 commit into from
Nov 3, 2015

Conversation

akarnokd
Copy link
Member

@akarnokd akarnokd commented Nov 2, 2015

I forgot a NotificationLite conversion in the constructor. Note that
there were no tests verifying null behavior at all.

I forgot a NotificationLite conversion in the constructor. Note that
there were no tests verifying null behavior at all.
@zsxwing
Copy link
Member

zsxwing commented Nov 2, 2015

👍

akarnokd added a commit that referenced this pull request Nov 3, 2015
1.x: fix scan() not accepting a null initial value
@akarnokd akarnokd merged commit eb65ba3 into ReactiveX:1.x Nov 3, 2015
@akarnokd akarnokd deleted the ScanAllowNull1x branch November 3, 2015 23:18
@akarnokd akarnokd mentioned this pull request Nov 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants