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

Delete scalaz.effect.IO #2038

Open
Milyardo opened this issue Feb 3, 2019 · 2 comments
Open

Delete scalaz.effect.IO #2038

Milyardo opened this issue Feb 3, 2019 · 2 comments

Comments

@Milyardo
Copy link
Contributor

Milyardo commented Feb 3, 2019 •
edited

With Task gone, it's now time to look at IO. Instead of deleting scalaz.effect outright however, I thought it best to raise an issue to see if MonadIO or any typeclasses in effect are worth salvaging. If they are should should scalaz-effect as a module remain and should these typeclasses be moved to core?
@emilypi
Copy link
Contributor

emilypi commented Feb 9, 2019 •
edited

@Milyardo I'm for moving the instances to core, and nuking scalaz.effect, but I'd like to gather opinions first.

@tonymorris
Copy link
Member

I agree, if it can be made to work. It was all the hack jobs that needed deletion, including Task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Milyardo @tonymorris @emilypi