viperproject / viperproject/silver
Parser errors not properly recognised on Viper Online
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 100
- Forks
- 53
- Avg merge
- 8h 10m
- Merged PRs (30d)
- 2
Description
Created by @mschwerhoff on 2019-09-03 16:05
Parser errors, such as reported for the snippet
field nxt: Ref
predicate P(x) { true }
are currently not properly recognised on Viper Online: the “Output” panel shows an error entry and includes the correct position information, but no error message. The “Original Output” tab contains the complete (but raw) error message.
See this permalink (if it works).
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the parser error in Viper Online with the provided snippet and permalink, then inspect how errors are transferred to the Output panel versus the Original Output tab. Done means the Output panel displays both the parser error message and its position information, rather than only the position.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100