Improve Data.Type.Equality.== another way

Authored by dfeuer on Aug 10 2017, 1:41 AM.



We can leave (==) as an open family, but use a poly-kinded
structural equality helper to produce instances. If we want to
allow users to decide what equality means for their kinds, I think
something like this is the way to go. One further step would be
to make (==) an associated type of a kind class. This would
change the "syntax" for declaring instances, but would be
considerably more compact.

dfeuer created this revision.Aug 10 2017, 1:41 AM
dfeuer added inline comments.Aug 10 2017, 1:48 AM

If people *want* the old way for Type, we can surely have it still with this new machinery; I just figure we probably don't.

dfeuer updated this revision to Diff 13474.Aug 10 2017, 1:54 AM

Fix language pragma

bgamari requested changes to this revision.Sep 13 2017, 11:30 AM

If I'm not mistaken this has been superceded by D3835, yes?

This revision now requires changes to proceed.Sep 13 2017, 11:30 AM
dfeuer abandoned this revision.Sep 13 2017, 11:39 AM

I believe so.