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

refactor(Scheduler): clearify the signature which Scheduler.schedule() takes as work. #2078

Merged

Conversation

tetsuharuohzeki
Copy link
Contributor

Description:

  • For more readability, more consistently.
  • I think this would not be a breaking change by these reasons:
    • There are no problem if we pass the function which does not has this specifying.
    • There are no problem if we pass the function which has this: any or this: Action<T>.
      • This case is valid with the actual behavior.
    • If we pass the function which has this: SomeNonValidTypeWithAction<T>,
      then, basically, its code would be wrong.

@tetsuharuohzeki tetsuharuohzeki changed the title refactor(Scheduler): clearify the signature which Scheduler.scheduler takes as work. refactor(Scheduler): clearify the signature which Scheduler.schedule() takes as work. Oct 25, 2016
@tetsuharuohzeki tetsuharuohzeki force-pushed the clarify-this-of-Scheduler-schedule branch from 50ee953 to 8e77086 Compare October 25, 2016 20:13
@benlesh
Copy link
Member

benlesh commented Oct 25, 2016

@saneyuki the build is failing after this change.

@tetsuharuohzeki tetsuharuohzeki force-pushed the clarify-this-of-Scheduler-schedule branch from 8e77086 to 0d8864c Compare October 26, 2016 04:01
@tetsuharuohzeki
Copy link
Contributor Author

@Blesh

the build is failing after this change.

fixed.

@tetsuharuohzeki tetsuharuohzeki force-pushed the clarify-this-of-Scheduler-schedule branch from 0d8864c to 103f0ad Compare October 26, 2016 04:03
@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.217% when pulling 103f0ad on saneyuki:clarify-this-of-Scheduler-schedule into 0271fab on ReactiveX:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.217% when pulling 103f0ad on saneyuki:clarify-this-of-Scheduler-schedule into 0271fab on ReactiveX:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.217% when pulling 4e1d2cc on saneyuki:clarify-this-of-Scheduler-schedule into 89612b2 on ReactiveX:master.

…()` takes as `work`.

I think this would not be a breaking change by these reasons:

- There are no problem if we pass the function which does not has `this` specifying.
- There are no problem if we pass the function which has `this: any` or `this: Action<T>`.
  - This case is valid with the actual behavior.
- If we pass the function which has `this: SomeNonValidTypeWithAction<T>`,
  then, basically, its code would be wrong.
@tetsuharuohzeki tetsuharuohzeki force-pushed the clarify-this-of-Scheduler-schedule branch from 4e1d2cc to 124a048 Compare October 27, 2016 03:05
@coveralls
Copy link

coveralls commented Oct 27, 2016

Coverage Status

Coverage remained the same at 97.217% when pulling 103f0ad on saneyuki:clarify-this-of-Scheduler-schedule into 0271fab on ReactiveX:master.

@benlesh
Copy link
Member

benlesh commented Nov 4, 2016

:shipit:

@benlesh benlesh merged commit 9ec444e into ReactiveX:master Nov 4, 2016
@tetsuharuohzeki tetsuharuohzeki deleted the clarify-this-of-Scheduler-schedule branch November 4, 2016 19:17
@lock
Copy link

lock bot commented Jun 6, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants