-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Function to print prettier parse exceptions #59
Conversation
That's hilarious, I was just discussing this with @dysinger 3 hours ago. Yes, this is very much a desired feature. And with the new displayException method, we can make it even nicer for users of GHC 7.10. |
Oh, I forgot about the |
I'd recommend doing both a separate function and displayException, so that On Tue, Mar 31, 2015, 1:24 PM Daniel Díaz notifications@github.com wrote:
|
Since I had another user asking about this, bumping. Are you still planning on implementing this? |
…from Data.Yaml, and implement displayException for recent versions o base.
My apologies. Travelling and work have kept me away from this. I have included commits that finish implementing |
Note that when showing a |
Also, for the |
Function to print prettier parse exceptions
Thanks! |
Using
yaml
sometimes I find unpleasant to read parse exceptions produced byprint
. The function implemented in this PR tries to mitigate this. It is incomplete, but I wanted to know if the idea is worth before spending more time with it.