Avoid java compilation error when user code defines Get in a codatatype #6054
Conversation
This file contains 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
…-defines-get-in-a-codatatype
…-defines-get-in-a-codatatype
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.
What was changed?
The Java code generated for a codatatype always contained a method named
Get(). This would cause a conflict if the user defined a method with same name in this datatype, e.g. by:This PR changes the name of the automatically generated method to
_Get()to avoid name clashes. As Dafny method cannot start with an underscore_, it is safe to chose this name.How has this been tested?
Added test Source/IntegrationTests/TestFiles/LitTests/LitTest/git-issues/git-issue-4153.dfy
By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.