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

Better error reporting #27

Open
3 tasks
jprochazk opened this issue Mar 16, 2023 · 0 comments
Open
3 tasks

Better error reporting #27

jprochazk opened this issue Mar 16, 2023 · 0 comments

Comments

@jprochazk
Copy link
Owner

Currently we discard all spans from the AST. This means that errors coming from the VM cannot be traced back to source code. This could be fixed by:

  • Keeping track of spans for each emitted instruction, and storing those spans in function objects
  • Implementing a file database which allows emitting errors that span multiple files (in case Hebi is used in standalone mode)
    • The input to eval should somehow be excluded from this
  • Storing the file database in the Context, so that it can be used to construct errors anywhere you have access to it (which is almost everywhere)
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
@jprochazk