Skip to content
This repository was archived by the owner on Oct 4, 2020. It is now read-only.

Conversation

@coot
Copy link
Contributor

@coot coot commented Jul 5, 2017

This way one can use catchException to remove the effect type.

This way one can use `catchException` to remove the effect type.
@garyb
Copy link
Member

garyb commented Jul 10, 2017

Argh! This is definitely correct, but I think it would be too-breaking a change to release as a patch version... I'm not sure what to do about it really. 😕

@coot
Copy link
Contributor Author

coot commented Jul 10, 2017

Indeed :/. But it's really nice to know that at the top level of your app you don't have the EXCEPTION effect.

@garyb
Copy link
Member

garyb commented Jul 10, 2017

I guess for now a workaround would be to use a coercion like:

coerceErr :: forall eff. Eff (err :: EXCEPTION | eff) ~> Eff (exception :: EXCEPTION | eff)
coerceErr = unsafeCoerceEff`

@coot
Copy link
Contributor Author

coot commented Jul 12, 2017

Yes, this is what I use at the moment.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants