Closed wadoon closed 8 months ago
Attention: 16 lines
in your changes are missing coverage. Please review.
Comparison is base (
abbe1f8
) 37.98% compared to head (a8a10a8
) 37.98%. Report is 15 commits behind head on main.
Files | Patch % | Lines |
---|---|---|
...java/de/uka/ilkd/key/settings/GeneralSettings.java | 23.80% | 16 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This PR allows you to configure the enabled keys in the processing of the JML conditions within the JML conditional annotation texts. Currently, the set is hard coded and only contains
key
as the only enabled key. This means, that KeY accepts the following JML annotation texts:/*@ ...*/
/*+key@ ...*/
/*+key+openjml@ ...*/
but ignores
/*+openjml@ ...*/
/*-key@ ...*/
Intended Change
GeneralSettings
which contains a set of enabled keys.-PJML_ENABLED_KEYS=a,b,c
on the CLI, or$HOME/.key/proofIndependentSettings.json
.Currently, there is no GUI element to configure this element.
The need for this raises from case study where you want to have the same source code as the foundation, but you have different verification runs: e.g, functional behavior under overflow absence, and a second run to prove overflow absence. Now you can differentiate the specificaton between the runs. For example:
Question to the reviewer
Type of pull request