-
Notifications
You must be signed in to change notification settings - Fork 175
Typed holes treated as exceptions #536
Comments
Probably just needs the same fix as this: #438 (comment) |
Okay, I think I have this going now, but it obviously overlaps a lot with your link. Do you want to wait for that fix to come in, or should I open a PR for this bit? Edit: Not sure how I forgot this: thank you! Tracking that down was turning into a very deep rabbit hole without any apparent satisfying conclusion. |
Some additional commentary for the record, this is a tragic bit of the GHC API. |
I suppose we can always ask them to expose that? Then at least the workarounds can be removed in like 6 years? (3 major versions from now xD). |
What do you mean by overlap? Just rebase your stuff on top of serras' I was going to merge that anyways. |
The simple patch is to replace the definition of I talked to Austin a little about fixing this in GHC. He's still on vacation, but when he gets back he can help get these through since it really is a silly mistake in the GHC API. |
Just rebase on top of his branch he doesn't have time to work on this stuff ATM. |
Actually you can also just cherry-pick the commit if you like. |
Done #539 |
If you try to get
info
(ordoc
) on an expression within a module that includes typed holes,ghc-mod
is tripped up by an exception regarding the typed hole.Expected result: typed holes shouldn't stop
info
ordoc
from working. I'm taking a quick look at this now; any guidance is appreciated.The text was updated successfully, but these errors were encountered: