Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upEta expansion is required for higher rank types with constraints #950
Comments
garyb
added
bug
typechecker
labels
Mar 8, 2015
paf31
added this to the 0.8.0 milestone
Aug 8, 2015
This comment has been minimized.
This comment has been minimized.
|
I did some more work on this, and I'm not sure there is an elegant solution. We could add a case to the I think we should close this and work on eta reducing the dictionaries if we can. |
This comment has been minimized.
This comment has been minimized.
|
Another option: we modify the
|
This comment has been minimized.
This comment has been minimized.
|
The latter option sounds good to me, are there any downsides to it? My main reason for opening this is not that it's really all that bad, as there is a workaround at least, but it definitely seems like a wart. From the error message it is really not clear at all what is going on or that eta expansion would fix the error. |
This comment has been minimized.
This comment has been minimized.
|
Moving to 0.9. |
paf31
modified the milestones:
0.9.0,
0.8.0
Nov 16, 2015
paf31
modified the milestones:
0.9.0,
0.10.0
Apr 10, 2016
paf31
modified the milestones:
0.10.0,
1.0.0
Sep 17, 2016
This comment has been minimized.
This comment has been minimized.
|
I don't think we can bake eta reduction into the subsumes rule actually. Notice that I would really like to avoid any sort of eta conversion in the elaborator actually. I'll think about how we might be able to fix this in the typing rules instead. |
garyb commentedMar 8, 2015
This might already be known: