Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Why don't you use GHC's Custom Type Error? #26

Open
Hogeyama opened this issue Dec 19, 2018 · 0 comments
Open

Why don't you use GHC's Custom Type Error? #26

Hogeyama opened this issue Dec 19, 2018 · 0 comments

Comments

@Hogeyama
Copy link

The mechanism of indicating error using Elaborate type family is quite cool but now that extensible doesn't support older GHC, it can use GHC.TypeError to show more readable error messages. How do you think of it?

Example: I experimentally implemented it and found it useful when I can't remember the name of the field.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Hogeyama