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
I'm not 100% sure if my diagnosis is correct below, but I think this is an error.
I was doing some work splitting a type class and got to a situation where I believe some constraints are unambiguous, but Coalton considered them ambiguous:
Currently, it seems that type variable substitutions are only generated from functional dependencies when the variables in question are applied to the same class predicate.
Currently, it seems that type variable substitutions are only generated from functional dependencies when the variables in question are applied to the same class predicate.
This turned out not to be the issue. Rather, the issue was that superclasses were not considered when resolving functional dependencies in the typechecker.
I'm not 100% sure if my diagnosis is correct below, but I think this is an error.
I was doing some work splitting a type class and got to a situation where I believe some constraints are unambiguous, but Coalton considered them ambiguous:
All is good and well, and now we want to implement a function on
RandomAccessReadable
.With the declaration, we get an error:
Without the declaration, Coalton infers the following:
Since the functional dependency forces
:b
given:a
, Coalton is mistakenly not unifying (?):b
and:c
.The text was updated successfully, but these errors were encountered: