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.
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.