bytecodealliance / bytecodealliance/StarlingMonkey

Error stacks & code logs

Open
#27 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
288
Forks
57
PR merge metrics
No merged PRs in 30d

Description

As much as possible, all errors should provide a named and line-numbered source snippet indicating the location of the error.

Because we build sources directly, we can provide rich stacks for all errors, and should ensure that line numbers are properly displayed in this way for all error stacks through multiple call sites.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.