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
According to this note, it's possible for a plugin to generate new given constraints. Can we simply add quantified constraints like forall xs ys zs. ((xs ++ ys) ++ zs) ~ (xs ++ (ys ++ zs)) and then let ghc figure out whether it needs to apply them and avoid cycles? If that works, that would make using this library much safer, would make the implementation a lot simpler, and would probably support tricky wanted/given cases like in #3 !
The text was updated successfully, but these errors were encountered:
According to this note, it's possible for a plugin to generate new given constraints. Can we simply add quantified constraints like
forall xs ys zs. ((xs ++ ys) ++ zs) ~ (xs ++ (ys ++ zs))
and then let ghc figure out whether it needs to apply them and avoid cycles? If that works, that would make using this library much safer, would make the implementation a lot simpler, and would probably support tricky wanted/given cases like in #3 !The text was updated successfully, but these errors were encountered: