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

Explain in more detail why using MonadFix IO is undesirable #8

Open

rightfold opened this issue Mar 2, 2019 · 0 comments

rightfold commented Mar 2, 2019

The documentation of Tardis states:

Using a Tardis with no monad underneath will prove to be most common use case. Practical uses of a TardisT require that the underlying monad be an instance of MonadFix, but note that the IO instance of MonadFix is almost certainly unsuitable for use with Tardis code.

However, it is not clear why this is the case.

guibou mentioned this issue

Could not deduce ‘MonadFix m’ #15

Closed

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