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

Tasks, Concurrency, and Cancellation #177

Merged
merged 4 commits into from
Feb 18, 2018
Merged

Conversation

robotlolita
Copy link
Member

@robotlolita robotlolita commented Feb 17, 2018

Tasks are still experimental and they're developed in a fairly adhoc manner. This results in a lot of edge cases that are hard to cover under concurrent execution (races are always a pain), and makes it harder for people to reason about their code. #174 and #153 are examples of that.

The current PR includes an initial mitigation of #174 until Tasks are formalised. The common problems of cancelling tasks are solved by this, but there's no way of knowing if other edge cases exist without formalising.

You can try out these changes by installing version 2.2.0-alpha1, or just grab the @next branch:

npm i folktale@next

This is an initial mitigation  of #174 until Tasks are formalised. The common problems of cancelling tasks are solved by this, but there's no way of knowing if other edge cases exist without formalising.

The final solution will probably still involve linking tasks somehow so propagation works correctly, anyway.
@robotlolita robotlolita merged commit 5d520e2 into master Feb 18, 2018
@ghost ghost removed the in progress label Feb 18, 2018
@robotlolita robotlolita deleted the patch/task-cancellation branch February 18, 2018 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant