Skip to content
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

Improved treatment of final fields #3495

Draft
wants to merge 27 commits into
base: main
Choose a base branch
from

Conversation

mattulbrich
Copy link
Member

@mattulbrich mattulbrich commented Jul 6, 2024

Intended Change

Final fields cannot change their value after a single assignment in the constructor. In the current KeY logic, final fields are treated like normal fields stored on the heap. This is highly inefficient since heap assignments cannot have an impact on final fields at all.

The plan is hence to access final fields using a function of their own that does not depend on the heap, unlike other fields

T::select(Heap, Object, Field)   // for non-final fields
T::final(Object, Field)  // for final fields

The major challenges include

  • adapting reading of final fields in modalities
  • adapting accessing final fields in JML
  • handling constructors: they are allowed to write.

Writing must somehow be restricted since any modality could write to final fields and thus compromise proofs if thus different inconsistent values for final fields are around on a sequent.

Plan

  • Add functions for finals, add a taclet option
  • Implement rules that act upon those taclet options
  • Implement special treatment for constructors
  • Test effectiveness
  • Code cleanup
  • Document the changes

The following new items showed up:

  • Deal with prettyprinting of final fields using select. Currently o.f is the prettyprinting for both accesses.
  • Deal with parsing of final fields in JavaDL. o.f means something different now ...
  • static final fields are a challenge since they need double special treatment in parsing and prettyprinting

Type of pull request

  • Breaking change (feature that cause existing functionality to change)

The plan is to have a taclet otion to fall back to old behaviour.

Ensuring quality

To do:

  • I made sure that introduced/changed code is well documented (javadoc and inline comments).
  • I made sure that new/changed end-user features are well documented (https://github.com/KeYProject/key-docs).
  • I added new test case(s) for new functionality.
  • I have checked that runtime performance has not deteriorated.

Additional information and contact(s)

It is the modernised version of #3189.

@WolframPfeifer @wadoon

The contributions within this pull request are licensed under GPLv2 (only) for inclusion in KeY.

@mattulbrich mattulbrich self-assigned this Jul 6, 2024
@wadoon
Copy link
Member

wadoon commented Jul 6, 2024

Is #3189 now obsolete?

Interestingly, final is not so final on bytecode level.

@mattulbrich
Copy link
Member Author

Is #3189 now obsolete?

This is the commits from back then merged onto the modern main.

Interestingly, final is not so final on bytecode level.

There are a few source code level things that get lost on byte code. Also generics. Sometimes private fields are not so private in byte code. We operate on source code level and assume that all code is compiler-conformant.

... revert to heap updates in such cases.
@mattulbrich mattulbrich marked this pull request as draft July 6, 2024 21:33
@mattulbrich
Copy link
Member Author

The last commits add sound special treatment for constructors.

Copy link

codecov bot commented Dec 20, 2024

Codecov Report

Attention: Patch coverage is 59.29204% with 138 lines in your changes missing coverage. Please review.

Project coverage is 38.36%. Comparing base (db23498) to head (27f1584).
Report is 7 commits behind head on main.

Files with missing lines Patch % Lines
...src/main/java/de/uka/ilkd/key/pp/FinalPrinter.java 30.68% 54 Missing and 7 partials ⚠️
...a/ilkd/key/proof/init/FinalFieldCodeValidator.java 61.95% 20 Missing and 15 partials ⚠️
...kd/key/java/declaration/VariableSpecification.java 45.45% 6 Missing and 6 partials ⚠️
...ka/ilkd/key/proof/init/FinalFieldsPOExtension.java 76.66% 2 Missing and 5 partials ⚠️
.../de/uka/ilkd/key/speclang/njml/JmlTermFactory.java 0.00% 5 Missing ⚠️
...c/main/java/de/uka/ilkd/key/logic/TermBuilder.java 42.85% 2 Missing and 2 partials ⚠️
.../java/de/uka/ilkd/key/ldt/FinalHeapResolution.java 78.57% 2 Missing and 1 partial ⚠️
...e/uka/ilkd/key/rule/UseDependencyContractRule.java 0.00% 3 Missing ⚠️
...ka/ilkd/key/nparser/builder/ExpressionBuilder.java 60.00% 1 Missing and 1 partial ⚠️
...src/main/java/de/uka/ilkd/key/pp/FieldPrinter.java 89.47% 1 Missing and 1 partial ⚠️
... and 4 more
Additional details and impacted files
@@             Coverage Diff              @@
##               main    #3495      +/-   ##
============================================
+ Coverage     38.19%   38.36%   +0.17%     
- Complexity    17228    17341     +113     
============================================
  Files          2111     2115       +4     
  Lines        127642   127942     +300     
  Branches      21463    21512      +49     
============================================
+ Hits          48750    49084     +334     
+ Misses        72903    72819      -84     
- Partials       5989     6039      +50     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

it was not wrong before but not confluent. Failed the
case vstte10_05_Queue/AmortizedQueue_AmortizedQueue.key
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants