Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upVyper Support #300
Open
Vyper Support #300
Conversation
Closed
|
I have added a vyper-specific detector: For the long run, we need to add for each detector what language (Solidity and/or Vyper) is targeted. |
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.
I am starting a new PR from scratch to add the Vyper support (#191 has been abandoned).
Only the contracts and functions definitions are parsed. For now, the support is minimal; the statements are not parsed (and not converted to slithIR).
I have added a new tool:
slither-dependencies, which allows ensuring that all the external contract definitions are correct. Vyper does not support importing files, so the definitions are manually copied pasted, which is error-prone.