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

Delete the ever living shit out of Task #1401

Open
tonymorris opened this Issue Jun 8, 2017 · 4 comments

Comments

Projects
None yet
5 participants
@tonymorris
Copy link
Member

tonymorris commented Jun 8, 2017

It's 2017. Task still exists.

It's 2017

@kevinmeredith

This comment has been minimized.

Copy link
Contributor

kevinmeredith commented Aug 4, 2017

Could you please explain the problem with Task?

Would something else replace it?

Thanks!

@jdegoes

This comment has been minimized.

Copy link
Member

jdegoes commented Aug 4, 2017

Task has numerous unsafe functions, tries to be an IO monad but without providing all the time-tested functionality of such a monad (which it then tries to provide in more ad hoc ways), uses exceptions to communicate internally, uses implicits as global effectful values, and so forth.

That said, Scalaz 7 IO does not (by itself) subsume the functionality of Task, so Task in 7 cannot easily be deleted without causing user's pain. Scalaz 8's IO, however, will be a much richer version of IO that supports asynchronous effects, without any of the drawbacks of Task.

@fommil fommil added the scalaz7 label Aug 21, 2018

@fommil

This comment has been minimized.

Copy link
Contributor

fommil commented Aug 21, 2018

This is hopefully coming in 7.3. I created a dupe at #1874 (that was for 8.0) somewhere. I don't have the energy to find it right now.

@ktonga

This comment has been minimized.

Copy link
Member

ktonga commented Aug 22, 2018

@fommil I think you meant #1796

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment