Skip to content
This repository has been archived by the owner on Jul 1, 2021. It is now read-only.

More informative error reporting #7

Closed
3 tasks done
eschkufz opened this issue Sep 7, 2018 · 1 comment · May be fixed by #240
Closed
3 tasks done

More informative error reporting #7

eschkufz opened this issue Sep 7, 2018 · 1 comment · May be fixed by #240
Labels
enhancement New feature or request

Comments

@eschkufz
Copy link
Contributor

eschkufz commented Sep 7, 2018 •
edited

Overview

In general, let's make the user's life easier: both for handled and unhandled errors. When we're done with this, let's update the README to show off the new interactions.

Deliverables

  • Line and file numbers for errors, not just snippets of code
  • Best effort crash dumping
  • Updated README

Let's hold off on this until we have a clear idea what we want out of runtime logging. There's no sense in doing it for its own sake as busy work right now.
@eschkufz eschkufz added the enhancement New feature or request label Sep 7, 2018
@eschkufz
Copy link
Contributor Author

After a fair bit of hacking, we now produce file and line number details for parse and type checker errors. Now to beautify them a little bit.

@eschkufz eschkufz mentioned this issue Sep 17, 2018
Merged
2 tasks
@eschkufz eschkufz mentioned this issue Apr 15, 2020
Open
2 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Issue 7 eschkufz/cascade
1 participant
@eschkufz