New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introducing a new function symbol seqUpd #3385
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice addition!
I see one minor problem for the code quality: The relevant classes/tokens/methods are sometimes called seqPut
, sometimes seqReplace
, sometimes seqUpd
. I think that this is quite confusing, in particular for new developers. Can we just name everything consistently seqUpd
?
# Conflicts: # key.core/src/main/java/de/uka/ilkd/key/ldt/SeqLDT.java
Class names are allowed to remain historic. They are not used anymore since assertions and set statements avoid recoder. Recoder will be removed soon anyway.
# Conflicts: # key.core/src/main/java/de/uka/ilkd/key/ldt/SeqLDT.java
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we can get of the current ghost declaration processing, we might be able to get rid of the Recoder JML AST classes!
Change requests is blocking merge. Mattias clearly stated that you prefers the current state. It is only a minor readability/convinience thingy.
Intended Change
There was no explicit update function for sequences in KeY (any more). I added
seqUpd
for that purpose.The axiomatic rules is in
seqRules.key
and essentially reads:Type of pull request
Ensuring quality
The contributions within this pull request are licensed under GPLv2 (only) for inclusion in KeY.