Multi-file: Runtime error spans are incorrectly mapped to source files
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 212
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 65
Description
The bug exists in `run()` in the wasm layer. When the runtime error contains a span, and the span is coming from a file in the program that's _not_ the first one, the wrong span is reported.
I don't think this span is used in the UX anywhere but since it's such a general function it may bite us in the future if we decide to surface these spans.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting run() in the wasm layer and trace how runtime error spans are mapped when a program contains multiple files. Reproduce an error whose span comes from a file other than the first, then verify that the reported span points to the correct source file and location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100