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.

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

Errors should include a stack trace #16

Open
mariusae opened this issue Nov 8, 2017 · 0 comments
Open

Errors should include a stack trace #16

mariusae opened this issue Nov 8, 2017 · 0 comments

Comments

@mariusae
Copy link
Collaborator

mariusae commented Nov 8, 2017

Reflow isn't always very helpful when it errors. When execs fail, it provides a good deal of context, but other errors (e.g., stdlib errors, pattern matching errors, etc.) don't provide good context.

We should simply print a (Reflow) stack trace on every error, as this usually provides helpful context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant