Skip to content

perform_sequence: a higher-level, more debuggable way to perform with a SequenceDispatcher #69

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 8 commits into from
Aug 25, 2015
Merged

perform_sequence: a higher-level, more debuggable way to perform with a SequenceDispatcher #69

merged 8 commits into from
Aug 25, 2015

Conversation

radix
Copy link
Contributor

@radix radix commented Aug 25, 2015

The main benefit over SequenceDispatcher is:

  • you don't need the with, since it performs the effect for you
  • it generates a log of intents that were performed (or failed to be performed). omg!

radix added a commit that referenced this pull request Aug 25, 2015
@radix
Merge pull request #69 from python-effect/perform-sequence
12ff4dd 
perform_sequence: a higher-level, more debuggable way to perform with a SequenceDispatcher
@radix radix merged commit 12ff4dd into master Aug 25, 2015
@radix radix deleted the perform-sequence branch August 25, 2015 17:07
@radix radix mentioned this pull request Aug 25, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@radix