slither

Author	SHA1	Message	Date
Josselin	c29e080109	Add support for FileScope with cycles in the imports The implementation is not the most efficient as it can iterate a lot before reaching a fixed point, but ultimately the filescope should not contains too many objects and the iteration should be fast to converge. But we will need performance testing to see if there is an speed impact.	3 years ago
Josselin	5149497294	Fix pylint on test_features	3 years ago
Josselin	224d7a848a	Minor	3 years ago
Josselin	8d3faf2cba	Minor	3 years ago
Josselin	29ca3ce761	Refactor core objects to add a file scope. This is a significant refactoring that will allow slither to have a better support for codebases with naming collision (including contracts and structures) - Add core.scope.scope.FileScope, which represents all the objects accessible given a filename - Use this scope everywhere an access to another object is needed during parsing - Replace CallerExpression nammedtuple by a CallerContextExpression object. This cleans the python types and reduces the code complexity - Add test_features which currently tests the contract name and structure name collision through the standard solc json input and import through node_modules Fix #912	3 years ago