Draft
Conversation
4ecc7ac to
0e7e297
Compare
Member
|
Agreed during meeting: Move to |
0e7e297 to
5a0ef3e
Compare
5a0ef3e to
812cd8d
Compare
bd87b0f to
6aed5af
Compare
6aed5af to
68426b5
Compare
68426b5 to
bd44701
Compare
bd44701 to
0744c12
Compare
0744c12 to
e15c746
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR brings a tool for rewriting the settings in KeY files to the new JSON-like format. A requirement to get rid of the old property-based interface.
Changes along the road:
\proofis also treated asEOFor not. In normal mode, the lexer stops at\proofso that the s-expr of the proof are not going through the parser.Plan
Type of pull request
\proof.Ensuring quality
The rewriting itself is done via the settings classes (load/store methods), as we are not morons, this should ensure settings equality.