You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why is this better? Because you can't use Coercible a (JSRef b) when b is ambiguous. It occurs to me that this constraint ought to work due to the type parameter of JSRef being phantom, but perhaps this is an issue with the implementation of Coercible (on GHC 7.8, anyway).
Anyway, even if this is a GHC bug, it seems cleaner to have this separation.
The text was updated successfully, but these errors were encountered:
The idea is to have something like this:
Why is this better? Because you can't use
Coercible a (JSRef b)
whenb
is ambiguous. It occurs to me that this constraint ought to work due to the type parameter ofJSRef
being phantom, but perhaps this is an issue with the implementation of Coercible (on GHC 7.8, anyway).Anyway, even if this is a GHC bug, it seems cleaner to have this separation.
The text was updated successfully, but these errors were encountered: