Changed how Schedulers get their Schedule.#219
Merged
bmorris3 merged 1 commit intoastropy:masterfrom Aug 15, 2016
Merged
Conversation
Contributor
Author
Contributor
|
Should this be merged before your docs/tests updates for scheduling (#218), so that you can rebase that PR afterwards and include this new API change? |
Contributor
Author
|
That would be good. |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I moved the
Scheduleto be something created by the user and given to theScheduleras part of the call. This means that theSchedulerinitialisation doesn't need start/end times anymore. This also means that a user doesn't need to useschedule = scheduler(blocks)and is reflected in the changes to the tests.