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.

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

Investigate usage of Task.value(null) #133

Open
jodzga opened this issue Aug 8, 2017 · 0 comments
Open

Investigate usage of Task.value(null) #133

jodzga opened this issue Aug 8, 2017 · 0 comments
Assignees
@hiteshsharma

Comments

@jodzga
Copy link

jodzga commented Aug 8, 2017

Task.value(null) shows up in real code in places where there are deficiencies in ParSeq's API, see #132 or where it is not clear which existing API is supposed to be used.
This work is to investigate usage of Task.value(null) and if possible improve ParSeq API to avoid it's usage.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hiteshsharma hiteshsharma

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hiteshsharma @jodzga