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

[breaking] Proposal to move library to IO monad #6

Open
epoberezkin opened this issue Oct 29, 2024 · 1 comment
Open

[breaking] Proposal to move library to IO monad #6

epoberezkin opened this issue Oct 29, 2024 · 1 comment

Comments

@epoberezkin
Copy link

UnliftIO increases costs and there is no need to have it in this library - it is better to keep library code in IO monad and have applications that use UnliftIO wrap it.

It would be a breaking change, but it would make it usable for a wider range of applications that don't necessarily use UnliftIO.

As a side note, we do use UnliftIO at the moment, but we believe it was a mistake to use it, and it is much better to use a fixed monadic stack than have MTL code that sometimes have problems with specialisation and can have leaks, and can by mistake create much taller monad stacks than you think you are using. It's a personal choice how to write applications, but it's better to keep libraries simple.

@epoberezkin
Copy link
Author

Or, at least move it to MonadIO

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant