viperproject / viperproject/silver
Termination Plugin: deactivated flag set to false when decreases removed from code
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 100
- Forks
- 53
- Avg merge
- 8h 10m
- Merged PRs (30d)
- 2
Description
In particular, TerminationPlugin.mapVerificationResult in https://github.com/viperproject/silver/blob/master/src/main/scala/viper/silver/plugin/standard/termination/TerminationPlugin.scala#L125 performs a non-trivial transformation in the following case:
method foo()
{
assert false
}
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 in src/main/scala/viper/silver/plugin/standard/termination/TerminationPlugin.scala at TerminationPlugin.mapVerificationResult around line 125. Reproduce the transformation using the provided foo method and inspect how the deactivated flag changes when decreases are removed from the code. Done means the flag retains the intended value for this case and the behavior is covered by a regression check.
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
- 35/100