Visibility #10
Merged
Visibility #10
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
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 address issue #1743.
For functions, all visibility specifiers were already handled syntactically and being added to the
<contract-fn-visibility>cell. For state variables, they can only be internal, private or public, so no need to handle external for them. When there is no inheritance, internal (accessed through current contract or contracts derived from it) would be the same as private. Public and private specifier were already handled.So, at this time, I think that all that is needed for this issue is to replace internal with private in our tests. Please let me know if you would like anything additional.