We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given that we support now compilation unit with multiple contracts with the same name, we might need to revisit
slither/slither/core/declarations/function_contract.py
Lines 24 to 31 in 4c976d5
And similar definition of canonical_name, as it might create issues.
canonical_name
One solution would be to use the source mapping definition of the contract to ensure uniqueness.
Related: #1535 (comment)
The text was updated successfully, but these errors were encountered:
Related: issues when contracts have the same name #1372
Sorry, something went wrong.
No branches or pull requests
Given that we support now compilation unit with multiple contracts with the same name, we might need to revisit
slither/slither/core/declarations/function_contract.py
Lines 24 to 31 in 4c976d5
And similar definition of
canonical_name
, as it might create issues.One solution would be to use the source mapping definition of the contract to ensure uniqueness.
Related: #1535 (comment)
The text was updated successfully, but these errors were encountered: