viperproject / viperproject/silver
Allow front-ends to pass error messages down to Silver and back-ends
Open
Nobody has claimed this yet.
enhancement
minor
- Dominant language
- Scala
- Stars
- 100
- Forks
- 53
- Avg merge
- 8h 10m
- Merged PRs (30d)
- 2
Description
Created by @mueller55 on 2014-09-08 12:11
Silver has info-fields, but so far they are not populated by front-end and not used by the back-ends.
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
Start by tracing Silver's info-fields and the interfaces between front-ends, Silver, and back-ends. Determine where front-ends can populate the fields and where back-ends consume them. Done means error messages pass through Silver and are available to back-ends.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100